On 19 September 2010 03:11, Waqas Hussain <[email protected]> wrote: > On Wed, Sep 15, 2010 at 8:44 AM, Justin Karneges > <[email protected]> wrote: >> In trying to reduce the number of network round trips in our plain (non-XMPP) >> BOSH implementation, I wonder about putting data in the session creation >> request and response <body> exchanges. In XEP-0124, there is no mention >> about >> whether the body must be empty in either case, but all examples show it >> empty. >> However, XEP-0206 has an example of the server replying with >> <stream:features> >> in the response, so at least that much seems to be allowed, right? I want to >> know if putting data in the initial client request is allowed too. >> > > It's not disallowed, which I take to mean it's allowed. >
I'd rather it be disallowed. It makes no sense for the client to send anything prior to stream features. I'm certainly in favour of the server being able to include data in the creation response, that's just natural (and I thought it was in the XEP already - we have discussed it before). >> XEP-0124 could probably use some clarification on this, particularly if it is >> allowed. >> > > +1 > +1. >> One caveat of an initial data exchange is that the client doesn't know the >> sid >> yet, and therefore it cannot retransmit requests in the event of failure. >> This means you'd only want to include initial data if loss or dups are >> acceptable (such as the case with stream:features in XEP-0206). >> Just one reason it should be disallowed in my opinion, it breaks what is otherwise a fairly clean protocol handshake. That said, I just noticed you said in your original mail that it's non-XMPP BOSH you're working on. In which case perhaps there is more of a case for allowing initial data from the client. In which case perhaps it should be allowed in -124 and disallowed in -206. Just a thought. Matthew
