One of the requirements for the new protocol is that there are no 'text' messages generated by the service - the client will be responsible for generating these. The only case in which a text message will be appropriate would be for extensions to conferencing which are not required to participate within a channel, but still need representation in a client.
For instance, say there was an extension to allow you to remove people from a room. If you are an admin and remove someone, there would be a message with an xml namespace describing what happened, but also a generated text message for use in clients which do not support the removal notification. If there was a 'reason' you specified for kicking the poor fellow, that could either be in the form of a text message embedded in the XML, or as a set of predefined codes.
I also want to add an extension to generic conferencing for rooms which track the real jabber ID of the local participants, which would definately help with tracking real names - without that feature, the participants in the room will be anonymous. That is still a little ways off though.
Don't worry, I post something publicly as soon as I'm done. If anyone wants a rough draft while I'm working on it, just shoot an email or IM my way ([EMAIL PROTECTED])
-David Waite
Robert Temple wrote:
Jens, I completely agree on all 3 points. Hopefully the final conferencing protocol will work some other way. The current draft seems like its just IRC wrapped into jabber, sans the ping/pong.-Robert-----Original Message-----The conference/groupchat server will post user-visible messages about people joining/leaving the chat room, e.g. "jens has arrived." These are problematic for several reasons:
From: Jens Alfke [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 21, 2001 4:55 PM
To: [EMAIL PROTECTED]
Subject: [JDEV] Server-generated conference messages are a problem
(1) They are localized by the server, not the client, so they don't necessarily match the language used by the client or by the rest of the conversation in the chat room.
(2) They refer to people by their nicknames; by contrast, my client is going to make efforts to look up real names and use those in its UI whenever possible (unless the chat room disallows this.)
(3) They assume the client's GUI wants to use text messages to indicate people joining or leaving. While this is true of the boring old textual chat UI that everyone uses, I have different ideas and these messages are getting in my way.
For the above reasons I would like my client to just ignore these messages and manage its own UI for showing people joining/leaving. However, I'm worried that the server may send out messages for other reasons either now or in the future. Are there any other types of messages that the chat room sends by itself, which I may not want to drop on the floor and kick into the corner?
-Jens
