Quick Summary:

The server is broken into multiple applications, one main "router" process called jabberbox and sub processes called "transports".  The
source for jabberbox is in this folder, each transport is in it's own sub-folder. 

The main process, jabberbox, starts and listens on a file socket for connections from local transports, and on a network socket for
incoming packets from other servers.  Local transports start up and hook up to jabberbox via the file socket, and then recieve/send all
of their external data through it. 


Getting Started:

For now, just type 'make' to compile the jabberbox.  Then type './jabberbox -c config.x &' to run it in the background.  You can look at
/ play with the config.x file before you start it if you want, but for sure you will have to change one thing in it, place your servers
name in the <name></name> tag if you will be testing out our server with other servers over the Internet.  You can also run it with a -D
option to print out lots of debugging information to STDOUT. 

After jabberbox is running, go to the jabber folder and type 'make' again.  Then start the jabber transport by typing './jabber.transport
-l /tmp/jabber.sock &' and it will talk to jabberbox and then start listening for net connections on port 5222.  You can also run it with
the -D option to see lots of debugging info. 

Now that it's all up and running, you can test it out with the command line clients or the windows client, or even simpler, cut and
paste(or type)  in the protocol samples from the web site(do a 'telnet localhost 5222').  It's also interesting to run jabber with the -D
option from one command line and paste in protocol chunks from another telnet window.

After the command line clients are working well, things will be a bit easier to play with.  Any help with making this whole process
easier(automated shell scripts generated from the Makefile :) is much appreciated! 

The Jabber Team
http://jabber.org/

