My original background is in robotics and computer-integrated manufacturing. In both, my interests centered on solving communication problems in mission-critical systems. At the beginning, that meant assembly and C programming as well as direct participation in the lowest levels of networking protocols. Forget TCP/IP and Ethernet?e were generating packets by hand on ArcNET networks.
Networks quickly evolved and the problem shifted to an increasing need to integrate the computerized factory floor into large-scale enterprise systems. Unfortunately, manufacturing systems are horribly heterogeneous, with each machine running completely proprietary software (often with one of a kind operating systems and programming languages). In addition, it is common for manufacturing machines to be kept in service for 20?30 years or longer. Long equipment life-spans result in a surprising number of shops still using tape drives, punch cards, and other ancient computer technology.
On systems where you have a full Java 2 Standard Edition (J2SE) or better environment, Java Jini (http://www.jini.org) provides a perfect framework for gluing the various bits together. In addition, it provides a common integration environment (Java) and elegant, distributed computing facilities, such as self-healing properties and distributed transactions. As J2SE begins to find its way onto more and more devices, Jini becomes an increasingly attractive technology for system integration and coordination.
Unfortunately, J2SE isn?t everywhere. The J2SE requirement for Java Jini proves to be a significant obstacle on proprietary or limited platforms. We needed a lightweight, flexible communication system to extend into these environments.
Jabber first came to my attention in late 2000. Peer-to-peer frameworks like Gnutella and JXTA were hot but lacked the robustness and predictability needed. Instant Messaging (IM) seemed like a much more promising solution.
Despite strong developer interest in IM technologies, there really wasn?t much out there. The largest IM systems are highly proprietary and unusable for systems where you may need to implement, extend, or control the servers. After some searching, it looked like a dead end. It appeared simpler and less expensive to create our own lightweight communication protocol from scratch.
Then I came across Jabber. It is open source, and exploits the very best features of XML, another hot technology. I was familiar with XML and understood the fundamental benefits driving its hype but had yet to see a compelling reason to use XML in my software. Jabber appeared to be that application.
Digging deeper into Jabber revealed a design that was simple and flexible. I?m a firm believer in the KISS philosophy so the appeal only grew. I decided to start playing with the technology.
What finally converted me into a Jabber evangelist was the active and enthusiastic Jabber development community. Jabber is a young technology being shaped on a daily basis by corporate, student, and hobbyist contributors. Although the core of Jabber is relatively stable, many important related technologies such as Jabber security are still under active development.
You have the opportunity to make crucial decisions that shape the future of Jabber IM technology even while Fortune 500 companies are using Jabber today for critical services. In addition, the Microsoft-driven hype behind SOAP and other XML-related technologies has ignited interest from various parties in using Jabber as a way to plug into the web services world without having to become Microsoft shops. Developers like you and me are making decisions today that will determine how Jabber grows to meet tomorrow's challenges. These challenges and their potential rewards are truly exciting. Come and join us!