This layer provides the basic communication from java servlets to a Jabber server.
Basically RegisterUser.java is provided as an example of a servlet written using ServletComm to register a user.
In general, a servlet can be called directly from html (registeruser.html) or can be more integrated, as in the case of an applet (appletregisteruser.html).
To enable configurability, there can be a configuration file (jabberhttpservlets.config) which can override the options compiled in from Config.java.
Within a servlet, reading of the configuration file can be turned off. This would be useful for a stable environment that is not subject to porting and tweaking.
Any servlet can be written to enable debugging of the xml streams to and from the Jabber server.
The return structure is just that, a structure being returned from functions. Because it is a structure, functions can have return codes, messages, return strings, etc. to provide more information in an expandable way.
registeruser.html is included as an example of an html interface.
appletregisteruser.html is included as an example of an applet user registration interface. In this file the Jabber server name is hidden so I wouldn't have to change the Servlet code. Basically since an applet has it's own sandbox, it shouldn't go to other Jabber servers.
However, the goal of this project is not to control the user interfaces.
Obviously the java and servlets can live on any platform, but this project will not address how to accomplish that on various platforms.
However, basic scripts that work on a linux type environment with Tomcat are provided to suggest possible organizational guidelines.
JabberApplet is another SourceForge project that utilizes some of the JabberHTTPServlets for increased functionality without added weight.