Okay, the software I wrote is a jabber client. A tiny rewrite
or addition to the C code would allow connection as a
component. You would not necessarily need to do this for your
intended purpose: sending messages. Just like bboard alerts,
messages can be from a single account
(bboard@openacs.org). However, my module also connects to
any jabber server as any user, assuming you have the
password, so each module could setup it's own connection and
send messages as it wishes. All you need to do is to write the
code that figures out the jabber user address
'user@domain/resource', build the xml (easy) and send. The
jabber coding only takes a few minutes.
Very cool, Tom.
