3 ms·

why is XMPP shite? just look: <message from="juliet@example.com" to="romeo@example.net" xml:lang="en"> <body>Art thou not Romeo, and a Montague?</body>

why is XMPP shite? just look: <message from="juliet@example.com" to="romeo@example.net" xml:lang="en"> <body>Art thou not Romeo, and a Montague?</body> </message> 69 chars just for the from/to. every. message. (more or less) There is already a concept of session, why send the full ID? not just a short ID. each byte costs energy, in this case most of the energy is spend on boilerplate, stuff that can be inferred much more cheaply. Fortunately its not wrapped in HTTP, as that'd add even more boilerplate each transaction.

y0ghur7_xxx 10y ago
https://tools.ietf.org/html/rfc6121#section-5.2.1 https://tools.ietf.org/html/rfc6121#section-5.2.1 because the message can be sent to different devices (resources) the user is connected with. This is not accidental complexity like you make it out to be. It is needed and wanted. Or are you advocating a binary protocol? Personally I really like the messages exchanged with xmpp: they are easy to understand and easy to craft. I think the success of http too, lies a little bit in the fact that it is human readable.
- KaiserPro 10y ago
  But they are not human readable. They are only readable by humans because can be converted to text with a text reader. For a protocol to be good, it needs decent debug tools. Yes I am advocating a binary protocol. If you want to have decent battery life, then you need to be efficient. This is the tradeoff you need to make. for something like text, I really don't understand peoples fear of binary protocols. As an aside clients have memory nowadays, there is no reason to send the full ID for the sender in each message (unless of course you are doing encyption, but even then, once you've exchanged keys its moot) a client needs to keep track of buddies that are online, so this data can be cached, and a local ID used instead.
daurnimator 10y ago
The 'from' is not sent for c2s connections The xml:lang element is rarely if every used.

y0ghur7_xxx 10y ago

https://tools.ietf.org/html/rfc6121#section-5.2.1 https://tools.ietf.org/html/rfc6121#section-5.2.1 because the message can be sent to different devices (resources) the user is connected with. This is not accidental complexity like you make it out to be. It is needed and wanted. Or are you advocating a binary protocol? Personally I really like the messages exchanged with xmpp: they are easy to understand and easy to craft. I think the success of http too, lies a little bit in the fact that it is human readable.

KaiserPro 10y ago
But they are not human readable. They are only readable by humans because can be converted to text with a text reader. For a protocol to be good, it needs decent debug tools. Yes I am advocating a binary protocol. If you want to have decent battery life, then you need to be efficient. This is the tradeoff you need to make. for something like text, I really don't understand peoples fear of binary protocols. As an aside clients have memory nowadays, there is no reason to send the full ID for the sender in each message (unless of course you are doing encyption, but even then, once you've exchanged keys its moot) a client needs to keep track of buddies that are online, so this data can be cached, and a local ID used instead.

daurnimator 10y ago

The 'from' is not sent for c2s connections The xml:lang element is rarely if every used.