hi Bernd, If a session is bound to more than one resource, how could we determine > which one to process with?
well, there are some places that use the initiating entity, and since we can get the bare jid from a full jid, i thought it wouldn't hurt to update the initiating entity to reflect the first bound resource. and some guys from [EMAIL PROTECTED] confirmed that too (though that's nothing official). > > I quickly scanned 5.1.1 and it mentions the full jid. > > Side-note: At any time, if there is something ambigious in the rfcs, I > recommend consulting [EMAIL PROTECTED] mailing list or the most current > BIS-revision of the RFC, for example at > > http://www.xmpp.org/internet-drafts/draft-saintandre-rfc3921bis-04.html#roster > The BIS-process is due to replace RFC by newer RFC. The BIS docs have a > clearer structure and more examples. thanks, that's good to know, because there are quite some places where the RFC is not clear or gives room for interpretation. > Proposal: If the client does not send full JID (FJID), then we check the > session for a unique resource id. If there is not exactly one, we return a > stanza error. Else, we proceed with the FJID we determined. > hm, i kinda really only want to return a stanza error when the rfc states to do so. as for the presence probing: the rfc states that only the first ressource in a session should to that, because all subsequent resource can use the presence information gathered for the first bound resource. (sry, a bit off topic). so, are you okay with something like this? (pseudocode) String resId = bindResource(this); if (resourcesForSession == 1) { modifyInitialEntity(resId); } return resId; Regards, Gerolf
