[Standards] [Operators] Future of XMPP Re: The Google issue

Alexander Holler holler at ahsoftware.de
Thu Dec 5 00:05:50 UTC 2013


Am 05.12.2013 00:30, schrieb Matthew Wild:
> On 4 December 2013 23:13, Alexander Holler <holler at ahsoftware.de> wrote:

>> Who said that custom parsers are necessary? Maybe modify was the wrong term,
>> but e.g. you might have same problems when you feed them with the initial
>> <stream:stream>, because doing so, you almost never would get a some
>> wellformed XML. ;)
>
> Hmm, no, streaming parsers don't care about receiving data in
> arbitrary pieces. That's why they're called "streaming" :)

Yes, they don't care, but a XMPP-server has to care about, as the server 
should refuse not-wellformed stanzas. So feeding it with the initial 
<stream:stream> might result in a problem (not hard to avoid, but still 
ugly).

Another ugly thing are those stream restarts, they don't fit very well 
into the XML syntax too:

"The initiating entity MUST send a new initial stream header to the 
receiving entity over the encrypted connection (as specified under 
Section 4.3.3, the initiating entity MUST NOT send a closing </stream> 
tag before sending the new initial stream header, since the receiving 
entity and initiating entity MUST consider the original stream to be 
replaced upon success of the TLS negotiation)."

Regards,

Alexander Holler



More information about the Standards mailing list