4 ms·
I don’t understand the point of taking an existing protocol – with fairly well defined syntax/semantics, which has presumably been tested at various parts of th
by jacobolus 14y ago
I don’t understand the point of taking an existing protocol – with fairly well defined syntax/semantics, which has presumably been tested at various parts of the stack, likely has existing conformance tests, &c. – and wrapping it in a new ad-hoc protocol which has (some subset of roughly) the same semantics, just for a syntax change? Big addition of new complexity for little tangible benefit.
Why not just use one of the existing Javascript implementations of an XMPP client, or if they’re unsuitable for whatever reason, make a new one?
- jkarneges 14y agoLately there's been discussion within the XMPP community about how web developers tend to prefer semi-proprietary connectivity solutions like Socket.io even though the XMPP standard and surrounding solutions predate these kinds of things. We believe a large part of the problem is the encoding format. For better or worse, the web (and I mean all of it, not just browser<->webserver side) is transitioning to JSON for just about everything. Yes, it often seems like pointless wheel reinvention, but that's what is happening. May as well embrace the trend in order for our work to live on. One funny thing about all this is that when XMPP was first created (as "Jabber" in 1999), XML was selected as the format because it was the current trend. In that sense XMPP was super hip in the beginning. Hard to believe now people look at XML and think it's a relic. With that in mind, I wonder what will happen to all these trendy JSON protocols being made today? Dinosaurs of tomorrow, probably. My feeling is that it's the underlying concepts that will live on, regardless of format.
- spin 14y agoI don't want to start some kind of "XML vs JSON" holy war, but I really do prefer JSON over XML because of how compact and readable it is. I really don't see JSON as a passing trend, I see it as (almost) the most compact, succint way to express hashmaps in both human-readable and machine-readable form. (XML is big, bloated, and bureaucratic.) (It's tragic that Crockford left in all the qoutes around the keys, though. We really don't need to type those quotes.) For the past couple of years, I really have been wishing for an "XMPP, but built on JSON, not XML". Really. I want this.
- deno 14y ago> For the past couple of years, I really have been wishing for an "XMPP, but built on JSON, not XML". Really. I want this. The X in XMPP stands for extensible not XML. The reason XML fits the bill is because it has concept of namespaces, what JSON has? If you don’t have explicit namespace support how do you make your JSON variant of XMPP forward‐compatible? You don’t without making it look much, much, worse than any of the examples I’m about to show below. > (…) I really do prefer JSON over XML because of how compact and readable it is. > XML is big, bloated, and bureaucratic. My standard response to this is always “show me a JSON fragment that is shorter or prettier looking than an equivalent XML fragment.” XML can certainly be shorter than JSON and often is, and repeated tags are the best showcase for it: <user id="abc"> <phoneNo type="home">123456789</phoneNo> <phoneNo type="work">321654987</phoneNo> </user> This turns into this beautiful JSON: [ "users": [ { "id": "abc", "phoneNos": [ { "type": "home", "value": "123456789" }, { "type": "work", "value": "321654987" } ] } ] ] Oh, but what if order is important? Take this example: <policy id="123"> <drop someFilter="ghi" /> <accept someFilter="abc" anotherFilter="xyz"> <comment> This comment is quite long and spans several lines of text in pretty printed XML. But this is quite alright, because XML by default strips extra whitespace. </comment> <!-- That’s another kind of comment, but this one is not meant to be part of the data, unlike the one above. Some would say something as basic as comments is an essential part of so called human‐readable format… --> </accept> <drop someFilter="foo" anotherFilter="bar"> <reason statusCode="690">No reason</reason> </drop> </policy> Now you have to do it like that: [ "policies": [ { "id": "123", "rules": [ { "type": "drop", "someFilter": "ghi" }, { "type": "accept", "someFilter": "abc", "anotherFilter": "xyz", "comment": "Unfortunately the best you can do with JSON is to rely on your editor’s dynamic wrapping. And this is how you break the line: \nWhat a treat!", }, { "type": "drop", "someFilter": "foo", "anotherFilter": "bar", "reason": { "statusCode": 690, "message": "No reason"} } ] } ] ] For an example of how horrible JSON in wild can really be see Reddit’s JSON API. Because JSON has no syntax for metadata you get things like that: [ { "kind": "thing-foo", "items": [ # # list of comments or something that goes on for # two screens # ], "votes": 15 } ] See the keys are sorted for convenience. XML’s text representation is very minimal and consistent. You don’t need to quote Every Single Thing, and there are no special cases for not quoting just some type of values. The only redundant part of XML is repeating the name of the closing tag if the </element> has value. But this actually aids readability, as demonstrated above. Editing complex JSON by hand with a regular text editor is a nightmare, because of all those single '}', ']' and commas trailing for several lines when there’s any light nesting involved. Editing XML by hand on the other hand is no big deal.
- jakerocheleau 14y agoI don't have an answer but I do have a follow-up question. There are no pre-built GChat clients and I have been planning to create one using Phono, which is built on jQuery. Are there better solutions other than this, or the linked example Superfeedr? Google Chat is my main IM client and I know it's built on XMPP. I just want to pick a solid JS library to build with and make a web interface that can work for people.
- shmerl 14y agoYou can also use something like Strophe.js to build your own client. Or you want to add an XMPP/Jingle support as well? How exactly would it work, through routing Jingle over WebRTC? Update: I just looked at Phono - it doesn't seem like it supprots XMPP/Jingle, even though it uses WebRTC. So this kind of defeats the purpose, since you can't initiate audio/video calls to other XMPP clients. Can you advise any combinations of JavaScript client libraries and XMPP servers (i.e. without a need to use third party gateways) which can already normally support XMPP over WebSockets and Jingle over WebRTC?
- mweibel 14y agoXMPP over Websockets is implemented in various servers: - Prosody (http://code.google.com/p/prosody-modules/wiki/mod_websocket) - openfire (http://code.google.com/p/openfire-websockets/) - Tigase (built-in as far as I could see) - Ejabberd in the Commercial version, the opensource version doesn't really have one yet. Regarding Jingle over WebRTC: Various people are working on it (or have been, in my case) and it's getting closer to workable. What I encountered, when I tried ~a year ago to do it, was that not all SDP messages could be easily transformed into the Jingle format. Might have been changed now though as the WebRTC Specs have changed quite a bit.
- shmerl 14y agoThanks for the pointers. I hope open source ejabberd will catch up, since I prefer it in general. Are any of the Jingle through WebRTC projects public to track their progress?
- shmerl 14y agoI agree. It's better to help improving current XMPP libraries for good support of WebSockets and etc. instead of bringing JSON into the picture.