In the beginning there was Jer and then there was Jabber. Melodramatic? Sure.
Jabber.com came about in March 2000 and the Jabber Open Source guys were creating release version 1.0 http://jabber.org .
May 1, 2000 ... I joined Jabber.com http://jabber.com and we set about telling the world about Jabber.
As we began creating custom clients, the first servlets came about. Designed to empower customers who didn't want their users to have rosters and to provide additional functionality for thin clients.
They work. I've installed early versions on client sites and more recently they are providing functionality for JabberApplet http://jabberapplet.sourceforge.net another SourceForge project.
As I continued to use these in various applications, I wanted a base library that would provide debug capability, ease of writing xml streams for Jabber communications (I got tired of escaping things), and could be independent enough to support applets or straight xml interfaces, and even Java applications.
Sample html files (with cool things like stylesheets and JavaScript) and sample httpservlets have been provided, but the door is wide open to create what you will.
It will not be the focus of this project to control a ui, I have been involved in way too many customizations that would be difficult to maintain and gain concensus upon.
I'm in the process of writing apps that will require a real parser, and at this time am leaning towards Xalan which uses Xerces, and provides XSLT capabilities.
There are baby parse routines embedded, but these are not meant to supplant an xml parser.
The first time I met Jer, temas, tsbandit, and dizzyd we all played a game of Mech Warrior. From that I got the idea of a JabberMek. A mek powered by Jabber, hence my nick and a name for another project.
Originally presented to you by Flint aka jmek aka Flint Hoskins