This module turns AOLserver into a client, which can communicate with a Jabber Server. Each client would take up at least two threads: one for the connection to the Jabber server and one for the display of incoming messages. I suppose the display could be an auto refresh type deal, but it still seems kind of expensive for large scale use. Intranets might be a different story.
What seems like it would be easy to do is:
- Send messages instead of email, since jabber stores your messages when you are offline.
- Record groupchat. I have already set this up without OpenACS.
- Maintain a whose online database.
- Record a weblog -done.
- Provide a way to send messages to an OpenACS discussion bboard.
- Provide a "box" where web users could send a message to a jabber groupchat, chat or jabber user, probably by maintaining the user@server/resource and password, and a list of buddies you want to know about.
- Provide a way of creating a jabber groupchat room -done.
I guess it really is up to what we need and can live with for IM in OpenACS. Anyone have an opinion?
