I just looked over the Multi User Chat spec for Jabber...
Quote:
The additional features and functionality addressed in this JEP include the following:
1. "native" conversation logging (no bot required)
2. enabling users to request membership in a room
3. enabling occupants to view an occupant's full JID in a non-anonymous room
4. enabling moderators to view an occupant's full JID in a semi-anonymous room
5. allowing only moderators to change the room subject
6. enabling moderators to kick participants and visitors from the room
7. enabling moderators to grant and revoke voice (i.e., the privilege to speak) in a moderated room, and to manage the voice list
8. enabling admins to grant and revoke moderator privileges, and to manage the moderator list
9. enabling admins to ban users from the room, and to manage the ban list
10. enabling admins to grant and revoke membership privileges, and to manage the member list for a members-only room
11. enabling owners to limit the number of occupants
12. enabling owners to specify other owners
13. enabling owners to grant and revoke administrative privileges, and to manage the admin list
14. enabling owners to destroy the room
|
Sound at all like familiar, something like the features of a "dead" protocol?
Jabber as an IM client is cool, closer inspection of Jabber as a chat server shows that it's basically IRC with the added bandwidth/processing overhead of XML.
Example, this is the sample for a new user entering a room with 2 other users...
Quote:
|
<presence from='darkcave@macbeth.shakespeare.lit/firstwitch' to='hag66@shakespeare.lit/pda'> <x xmlns='http://jabber.org/protocol/muc#user'> <item affiliation='owner' role='moderator'/> </x> </presence> <presence from='darkcave@macbeth.shakespeare.lit/secondwitch' to='hag66@shakespeare.lit/pda'> <x xmlns='http://jabber.org/protocol/muc#user'> <item affiliation='admin' role='moderator'/> </x> </presence>
|
Or in IRC...
Quote:
RPL_NAMREPLY #channel :@user1 user2
RPL_ENDOFNAMES #channel :End of /NAMES list
|
Much more bandwidth friendly, to the point where the running costs on a busy server would be significantly lower.
I like XML for some things but am not convinced it's necessary or desirable for a streaming protocol, it's very wasteful of resources.