carpe decorum

After reading this post, and reading this (via: InternetWeek @
http://www.internetweek.com/columns01/lewis021301.htm)

"This doesn't mean AOL IM will become the foundation for all B2B application communications. But it does mean a new generation of products and services that looks an awful lot like IM systems will emerge to serve these needs. Jabber, for example, is an open-source IM client based on XML and managed by Jabber.org. At its core, Jabber consists of several components, including what is in essence an XML router, and other services such as presence management (which allows a communicating party to find out if another party is online). With the right security model, integration with directory services and other key functions, Jabber (or other systems like it) may well become the foundation for a message-oriented communications infrastructure that moves XML messages between applications.

"It's clear that message-oriented communications protocols that carry XML-encoded information and transactions will play an important role in creating the B2B infrastructure. And that means IM could move well beyond its roots and become a defining element for distributed computing on the Internet."

I finally took the time to debug and relaunch our enterprise IM server (jabberd). We have lots of enterprise application integration (EAI) to do this year, and I think Jabber is our friend in that arena. Particularly since the publication of Programming Jabber (http://www.amazon.com/exec/obidos/tg/detail/-/0596002025/103-3857919-5035858?vi=glance).

Jeez, this is more of a weblog post than a comment. Sorry for the rambling.

Ramblings are useful, as are the links. I had a vague recollection of something that worked to pull together data — instant messenger — from various programs, but had forgotten the thing. Jabber looks good then. Need to get GAIM working on my machine.