Tobias Markmann wrote:
Hi,
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?
Cheers,
Tobias
Hello,
as I understood, the "accept" attribute shows set of encodings CM can
accept from client. On contrary to encodings client can accept from CM
which are specified in Accept-Encoding HTTP header. Due to HTTP RFC,
Accept-Encoding can be only in requests so I guess this is a workaround
for letting client pick an encoding as well. Then, requests and
responses can be in different encodings, whatever it's good for.
But I think that if you'd encode second request in encoding you got init
response in (Content-Encoding of init response), it won't do any harm.
CM should know how to decode data with a method when it encodes with
that method.
rgds,
tomk
