Am 04.12.2013 23:22, schrieb Matthew Wild:
On 4 December 2013 22:09, Alexander Holler <[email protected]> wrote:
But the first hurdle everyone who wants to receive (and understand) XMPP
messages is to get some XMPP-parser on the start and modify it such, that it
can handle XMPP-streams. And that already does cost a lot of time. And I
think most people don't have much interest in writing their own XML-parser,
if all they want to do is to send and receive some messages.
It is a myth that XMPP requires custom parsers. Prosody uses a
completely unmodified Expat - any SAX parser should work just fine for
XMPP, and most languages and environments have one available.
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. ;)
And just using totally unmodified parsers might be risk, at least if you
don't use additional steps to prevent unwanted things like stanzas in
sizes which would eat your available memory, or that problem many expat
using XMPP-servers have had (can't remember if it was CVE-2009-3560 or
something else).
Regards,
Alexander Holler
