Comment 1 for bug 454952

Just collecting odd notes here:

 http://xmpp.org/extensions/xep-0045.html

XMPP messages at their core are "message", "presence", or "iq". IQ is a query/response dealio, and requires maintaining state on at least one end (rather like DCC I suppose).

Jabber MUC is descended from Jabber GroupChat 1.0 in a backward-compatible way, so you get these XML documents that look like nested "domish" dictionaries in twisted, and the MUC ones have an "x" tag inside that holds all the stuff that gc1.0 couldn't do.

Wokkel looks interesting, but we'll likely be implementing our own JabberRequest and JabberResponse objects anyway, which should encapsulate the details of the events a little better. Ideally I'd like for the basic message/action/notice type events to appear identical, so that a module can work for both.