Could you elaborate bit that convoluted and fragility opinion ? Well, there is no standard way in converting XML to JSON. Especially if avoiding JSON to be bloated. I went through all available resources and run tests with my pretty complex and big XMPP stanzas. In my tests this approach is in par, size wise, with original XMPP/XMP, in some cases even better.
My target was to create ease to use way to "talk" XMPP with JSON. Keep amount of JavaScript as minimum required for XMPP. Have server-side implementation also fairly simple with little or no overhead compared to XML parsing. -- Cheers, -Mika.H On Fri, 2011-05-06 at 01:31 +0530, ext Mridul Muralidharan wrote: > Not sure if there is a standard way to convert from xml to json and > vice-versa, but the scheme proposed seems very convoluted and > potentially fragile ... > > > Regards, > Mridul > > > > ----- Original Message ----- > > From: Peter Saint-Andre <[email protected]> > > To: Bidirectional Streams Over Synchronous HTTP <[email protected]> > > Cc: > > Sent: Friday, 22 April 2011 10:04 AM > > Subject: [BOSH] Fwd: [Standards] Proposed XMPP Extension: JSON > Content Type support > > > >T his is mostly BOSH-related so I thought I'd forward it here... > > > > -------- Original Message -------- > > Subject: [Standards] Proposed XMPP Extension: JSON Content Type > support > > Date: Wed, 20 Apr 2011 15:35:55 +0000 > > From: XMPP Extensions Editor <[email protected]> > > Reply-To: XMPP Standards <[email protected]> > > To: [email protected] > > > > The XMPP Extensions Editor has received a proposal for a new XEP. > > > > Title: JSON Content Type support > > > > Abstract: This specification defines JavaScript Object Notation > (JSON) > > use in XMPP service. > > > > URL: http://www.xmpp.org/extensions/inbox/json.html > > > > The XMPP Council will decide at its next meeting whether to accept > this > > proposal as an official XEP. > >
