Ivan, This XMPP and Jabber software is improving at warp speed.
I think I am on the agenda presenting this topic at the AG Retreat. The Jabber servers are pretty solid. We don't like the Jabber client. Gaim and Psi are the two clients I have used. There are many available clients and there are several xmpp libraries available. These come in many different languages including a python one we have used to build a special purpose client. We have been working to modify the Gaim client and the Jabber server so that X.509 certificates can be used for authentication and we plan to start adding components of the incremental trust model I talked about at the last WACE meeting. We are also working on good easy registration and user directory support interfaces via the web. To see a partial list of the clients and servers available go to www.jabber.org and look under software. Anyone interested in trying the protocols out is welcome to contact me and I can help you connect to our server. Deb Ivan R. Judson wrote: > > Hey Deb, > > Has the code base for the Jabber software gotten any better? The last time I > looked (about 12 months ago) it was doing very odd platform dependent things > and was amazingly convoluted inside. > > I'd be happy to imagine a pure python jabber server (stripped down to the > bare necessities) that could be run either stand-alone or incorporated into > the "service cloud" that a venue server is. > > FWIW, the current client design looks something like this: > > UI widgets <=> simple text processor class <=> text client class > > To facilitate not only this possibility but also other interesting choices, > I think adding a protocol parser like: > > UI widgets <=> presentation processor class <=> wire protocol processor <=> > text client class > > Means we can support a couple of combinations of the things it sounds like > the community wants: > > 1) MOO style syntax (by having a MOO style presentation processor class) > - although people could write IRC, or whatever > 2) XMPP (by having a XMPP wire protocol processor) > - Our current trivial protocol could also be written > 3) Network connection independence, the text client class can be responsible > for doing all the network stuff. > > Now, that's the client. What about the server? :-) > > I'd love to have a chance to chat about this at the ag retreat, let's plan > on having this as an agenda item in the developers sig at least. > > --Ivan > > >>-----Original Message----- >>From: [email protected] >>[mailto:[email protected]] On Behalf Of Deb Agarwal >>Sent: Monday, April 26, 2004 4:55 PM >>To: Todd Zimmerman >>Cc: [email protected] >>Subject: Re: [AG-TECH] Will the Moo resurface? >> >>Jabber is instant messaging similar to MSN and IRC but it is >>based on open standards. We have found it to be very >>reliable and the developer community is very active adding >>new features and capabilities. >>Using Jabber for AG chat would be more like the MOO paradigm >>where the chat was available regardless of whether the rest >>of the AG was. >> >>Deb >> >>Todd Zimmerman wrote: >> >>>This discussion actually has just come up within our >> >>WestGrid AG tech >> >>>community. We are currently discussing which text chat >> >>protocol to go >> >>>with. >>> >>>Two of the more useful aspects of the moo was its lack of >> >>integration >> >>>and its stability. The entire video conference could be collapsing >>>around you, but the moo was always there and you could >> >>always count on >> >>>it being there. >>> >>>It seems with AG2 that the text chat is the first thing to >> >>go, which >> >>>is a major problem. Just when you need the text chat, it >> >>stops working! >> >>>Hopefully the next AG version will solve a lot of these issues.... >>>Until then, since most of our group never had any >> >>experience with AG1 >> >>>(and the moo), our group is currently leaning towards IRC and/or >>>passing around MSN id's. >>> >>>Todd >>> >> >>-- >>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>~~~~~~~~~ >>Deb Agarwal e-mail:[email protected] >>MS50B-2239 phone :(510)486-7078 >>Lawrence Berkeley National Lab URL: http://www-itg.lbl.gov/~deba >>Berkeley, CA 94720 >>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>~~~~~~~~~ >> >> > > -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Deb Agarwal e-mail:[email protected] MS50B-2239 phone :(510)486-7078 Lawrence Berkeley National Lab URL: http://www-itg.lbl.gov/~deba Berkeley, CA 94720 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
