Difference between revisions of "BoshIssues"

Jump to navigation Jump to search
830 bytes added ,  09:28, 19 October 2012
Adding "JSON Content Type support" in incoming
m
(Adding "JSON Content Type support" in incoming)
Line 151: Line 151:
==HTTPS port==
==HTTPS port==
There is not an HTTPS port for BOSH.
There is not an HTTPS port for BOSH.
==JSON Content Type==
See http://xmpp.org/extensions/inbox/json.html
===Issue===
This proposed extension adresses a discussion that reoccurs every now and then. The inital discussion over this proposal pointed out that mapping XML to JSON is a bit problematic. Also it should be clear where we are aming at:
* Keeping BOSH as it is with XML and allow a JSON payload
* Translate the BOSH-layer to JSON
* Translate all of XMPP, including BOSH to JSON
This proposal seems to do the last.
===Status===
* Mapping issues of the translation needs to be fixed
* The aim of the proposal needs to be clarified
* It is unclear how big the need for this is
If there are enough people motivated to work on this, best form some a working group to clear up the issues.
===Note===
Also see http://xmpp.org/extensions/xep-0295.html (Humorous)
62

edits

Navigation menu