[jdev] A rapidxml fork for XMPP
Alexander Holler
holler at ahsoftware.de
Thu Dec 5 00:32:04 UTC 2013
Am 05.12.2013 00:25, schrieb Alexander Holler:
> Am 04.12.2013 23:49, schrieb Dave Cridland:
>> Since we've been discussing XML parsers a lot...
>
> I think many people misunderstood why I don't like XML.
>
> It isn't really because XML-parser are hard to use, it's because they
> are unnecessary for the simple task of sending and receiving messages or
> presence states.
>
> Of course, using one ready to use XML-parser does cost time because you
> need to know his API, otherwise bad things might happen.
>
> But my whole point is, that they are bloat in both, code and resource
> size (I know about in-situ parsers, but even those have to parse). And I
> don't see any reason why the stuff which goes over the wire should be in
> a "somewhat" human readable format. And with SSL, that human readable
> thing is already gone (on the wire).
>
> And, please, don't forget, that unholly discussion started because I've
> responded to a mail about M2M. And I wouldn't like it, if M2M wherever
> that term will end up, would use that bloat again.
Btw, what adds a lot of bloat too, is the textual representation of
tags. A XML parser usual doesn't care a lot about them, but a
XMPP-server/client has to compare every tag with the list of tags he
knows and wants to handle. That ends up in a lot of unecessary string
compares in comparision to a format where tags would already be
represented by simple numbers.
Regards,
Alexander Holler
More information about the JDev
mailing list