On Wed, Jul 23, 2008 at 11:17 AM, Stefan Strigler <[EMAIL PROTECTED]> wrote: > Hello Tobias, > > Am Dienstag, den 22.07.2008, 19:23 +0200 schrieb Tobias Markmann: >> I'm referring to Example 2 in XEP-124, >> http://www.xmpp.org/extensions/xep-0124.html#session-create . Don't >> the accepted encodings belong to the HTTP header instead of the body >> tag of the Session Create Response. The Session Create Request gets >> this right. It seems Content-Encoding field in the HTTP response >> headers would be best; or am I misunderstanding something there? > > One basic assumption of BOSH is to be able to deal with constraint > clients. One consequence in here is that a client may not be able to add > or modify ANY http headers. > > http://www.xmpp.org/extensions/xep-0124.html#reqs states: > > Compatible with constrained runtime environments** (e.g., mobile and > browser-based clients). > > **Compatibility with constrained runtime environments implies the > following restrictions: > > 1. Clients should not be required to have programmatic access to > the headers of each HTTP request and response (e.g., cookies or > status codes). > 2. ... > 3. Clients should be able to specify the Content-Type of the HTTP > responses they receive. > 4. > 5. > >
Ahh..okay...that's fairly understandable. :)
