ijgate is '''to be''' a gateway from a [jabber] conference room to a channel on [IRC] and is being written by [DG]

All clients in the jabber conference room will be expressed as irc clients that the gateway will manage.  In the inverse, all irc clients will be expressed as jabber clients by the gateway.  I will do my best to make sure the link is loss-less with regards to embedded attributes and do my best to give the illusion that everyone appears to be in a single "channel".

3.5 hours into it on day one, I have the irc agent part done, but with no implemention for how to create gateway services for jabber, I'm still reading the specs..  And to think some people have stated that jabber is a "simple" protocol..  hahaha   Go read the specs!

The job functions of the IRC ''Agent'' will be:
    * Shall be an operator in #tcl on irc.
    * When channel attributes and commands are given on the jabber side, the ''Agent'' shall execute those commands on the irc side.  ie: /kick, /ban, /title, /mode, etc...
    * same for the inverse.  When channel commands are given by other opers, the ''Agent'' shall execute the same on the jabber side. Ex. When someone who is a gateway'd jabber client is /kick'd from the IRC chat room, they shall be /kick'd from the jabber conference room as well.
    * For each client in the channel that is not being gateway'd from jabber, the ''Agent'' shall create their mirror in the jabber conference room.

[http://docs.jabber.org/general/html/component-intro.html]