Align session binding conflict with RFC1620 (#236)

Activities

wojciech.kapcia@tigase.net opened 1 decade ago

In RFC1620 a different approach than the one implemented in Tigase XMPP Server is encouraged, RFC 1620, 7.7.2.2.Conflict

Override the resourcepart provided by the newly connecting client with a server-generated resourcepart. This behavior is encouraged, because it simplifies the resource binding process for client implementations.

S: <iq id='wy2xa82b4' type='result'>
    <bind xmlns='urn:ietf:params:xml:ns:xmpp-bind'>
      <jid>
   juliet@im.example.com/balcony 4db06f06-1ea4-11dc-aca3-000bcd821bfb
      </jid>
    </bind>
   </iq>

Artur Hefczyc commented 10 years ago

I do not agree with the spec on this particular case. From our experience conflicting resources are almost always a result of connection/network failure and client reconnecting. Considering the old connection for the same resource as invalid is the best and most desired (by users and clients) action.

However, we should make Tigase compatible with the spec as many users or client expect Tigase to act in certain way described in the RFC. Therefore, I suggest we implement RFC behavior as a configurable option.

wojciech.kapcia@tigase.net batch edited 6 months ago

Name	Previous Value	Current Value
Iterations	empty	Candidate for next major release

Type	New Feature
Priority	Blocker
Assignee	wojciech.kapcia@tigase.net
RedmineID	1550
Version	Candidate for next major release

Iterations

Candidate for next major release Open

#214 Closed

One User login from two browser with same resource by bosh

Issue Votes (0)

Watchers (2)

Reference

tigase/_server/server-core#236