Hi Winfried, 'from' and 'to' is really confusing then and I don't quite understand the slight difference.
In my opinion, they should just be analog to: http://xmpp.org/rfcs/rfc6120.html#streams-attr-to "For response stream headers in client-to-server communication, if the client included a 'from' attribute in the initial stream header then the server MUST include a 'to' attribute in the response stream header and MUST set its value to the bare JID specified in the 'from' attribute of the initial stream header." I.e. if the client receives a BOSH Session Creation Response, the 'to' attribute should be the client's JID and the 'from' attribute is the server's identity. (And on the client's session creation request, they should just be vice-versa). Can't it be analog to that? As it stands, the client receives the response and the 'to' attribute contains "the identity of the backend server to which the client is attempting to connect"? That's weird. Christian Gesendet: Montag, 17. Februar 2014 um 12:36 Uhr Von: "Winfried Tilanus" <winfr...@tilanus.com> An: standards@xmpp.org Betreff: Re: [Standards] BOSH patches, hopefully the last before final On 11-02-14 13:54, Christian Schudt wrote: Hi Christian, Thanks for reviewing the patches and sorry for the delay in my response. > 1. Session Creation Response: > My suggestions concerning the 'from' attribute obv hasn't made it :-(.. Well, > so be it. > But I found this sentence: > 'to' -- This attribute communicates the identity of the backend server to > which the client is attempting to connect. > > Isn't it the same than the from attribute then? > Shouldn't the 'to' attribute be the client's JID in the server's response? Good question. Once again you are pointing to an issue where the history of the BOSH XEPs resulted in something that is a bit strange when you don't know the history. Remember that with the 'to' attribute the connection manager tells the identity of the backend server it is connecting to. The 'from' attribute 'MAY' be included once the connection manager established a session with the backend server and tells what identity the client has at the backend server. So they have a slightly different meaning. Also note that that backend server does not have to be a XMPP server. This has historically to do with the split of BOSH into two XEPs: generic BOSH (XEP-0124) and XMPP over BOSH (XEP-0206). Looking backward that was quite useless and even a bit confusing. But we are right now at the point where merging them again would only do more harm. > 2. Terminating the BOSH Session > Why did you remove the "<body/>" from this sentence: > > "... terminate the session by sending a <body/> element with a 'type' > attribute..." > ? Good catch, it is in the XML source, but I forgot escaping the brackets. Winfried
