That being said, as you indicated Gloox is C-based, and the reference implementation of SAX is in C. There is no excuse.
That being said, as you indicated Gloox is C-based, and the reference implementation of SAX is in C. There is no excuse.
I think rolling out your own XML parser for XMPP is a fairly reasonable thing to do. In the past at least, many, if not most, implementations had their own parser (often a fork of a proper XML parser). What is more surprising to me is why would they choose XMPP for their proprietary stuff. I don't think they want to interroperate or federate with anything?
(if I remember correctly and if it hasn't changed compared to many years ago, when I looked at that stuff.)
That is a common misconception, although I am not sure of its origin. I know plenty of XMPP implementations that use an XML pull parser.
I don't see any opportunity not to block when calling "next"