Noel, I wasn't familiar with jabber 'till you brought it up, but having looked at it today, and at Avalon based javajabber I think its a good idea. I think the client-server-client (cf p2p) model is a good one whereby James can add-value with combined mail/jabber account management and message processing (such as archiving or jabber<->mail) Also there's potential for james to use jabber to provide push notification to users, perhaps watching NNTP threads, or mail notifications. I'm thinking that users could possibly set up filters (through some kind of per-user mailet pipeline ;-)?) and be notified when mail or nntp messages raise events. I percieve a reluctance of traditional corporations to adopt p2p IM, perhaps because p2p is too amorphous and uncontrollable, after all even telephones are client-server-client, so with a c-s-c IM system organisations can monitor traffic metrics and message content in familiar ways, and perhaps feel more comfortable adopting IM.
I don't have the time to devote to it, but I like the idea, perhaps we should approach the javajabber guy? We might have jabber as another .sar (and so optional) and use jabber's own protocol to communicate with james. d. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
