Hi! On Tue, Aug 25, 2009 at 15:24, Niklas Gustavsson<nik...@protocol7.com> wrote: > If the client send a full JID, that is true. But, as in the case of > Smack, the client might not send a "from" attribute at all, in which > case we will need to figure out a resource anyways (not sure yet what > the best way is or if the spec says this somewhere).
Regarding the resource identifiers, I found this in the RFC3920: <quote> 3.4. Resource Identifier The resource identifier is an optional tertiary identifier placed after the domain identifier and separated from the latter by the '/' character. A resource identifier may modify either a <n...@domain> or a mere <domain> address. It usually represents a specific session, connection (e.g., a device or location), or object (e.g., a participant in a multi-user chat room) belonging to the entity associated with a node identifier. A resource identifier is opaque to both servers and other clients, and is typically defined by a client implementation when it provides the information necessary to complete Resource Binding (Resource Binding) (although it may be generated by a server on behalf of a client), after which it is referred to as a "connected resource". An entity MAY maintain multiple connected resources simultaneously, with each connected resource differentiated by a distinct resource identifier. </quote> Further in Section 7: <quote> 7. Resource Binding In general this applies only to clients: in order to conform to the addressing format (Addressing Scheme) and stanza delivery rules (Server Rules for Handling XML Stanzas) specified herein, there MUST be a resource identifier associated with the <n...@domain> of the client (which is either generated by the server or provided by the client application); this ensures that the address for use over that stream is a "full JID" of the form <n...@domain/resource>. </quote> Is the client not bound for MUC? If it is, there should be the resource (and hence, the full JID) available... somewhere. It's likely that I missed something, I was just skimming the mails. HTH anyways, Michael
