That is a browser issue, and does not exist in native clients. If we're talking about XML-stream-over-sockets, then comparing it to browsers makes no sense (bec

That is a browser issue, and does not exist in native clients. If we're talking about XML-stream-over-sockets, then comparing it to browsers makes no sense (because they can't do that!), and thus long-polling and JSON-over-HTTP become irrelevant. EDIT: Hmm, did you edit your post? I don't recall the first part being there... anyhow: > XMPP is too complex, but the XML stuff is really the smallest issue, compared with other complexities in the protocol. That is one factor, but the protocol complexities often seem to derive from the question 'how do we represent this in XML?', and that's an issue. Another problem is the jargon - the MUC specification is utterly incomprehensible, because the terms it uses for things are so wildly different from how they are used everywhere else, that building a mental model is really hard. I've seen this issue in other XEPs as well.