This is a developers release of a Jabber framework for Radio Userland.
This is NOT a conventional Jabber IM client for Radio Userland. There is
very little to see if you are not a developer.

Having got that out of the way ;-)

Download the following file and place it in your Tools directory:
http://www.jerf.org/resources/download/jabber.root . After it installs,
go to the homepage of the website (available from the Tools->Jabber menu
as "Documentation" and follow the instructions, which mostly consists of
"Run the installation", and has a couple of sample scripts.

The installation will create system.verbs.builtins.jabber, add an agent,
and create user.jabber . Again, if you don't know what that means, this
is probably not something you'll be interested in.

There's other documentation to poke around in, too.

Dann Sheridan has graciously allowed us to use his Jabber server while
testing this framework. You'll find the framework will use his server by
default. You may use any server you wish, of course, but I prefer not to
burder Jabber.com's main server.

The capabilities of this release are:
* Can listen to messages and respond to them.
* Can make and handle user-to-user XMLRPC calls over Jabber.

That may not sound like much now ;-), but there is room for growth. Much
of the hard parts are basically done, now we can add the cream.

I will be standing by in email, of course, but I will also be reachable
at Jeremy@.../Human . (Don't forget that last part, or you
may get Radio Userland on your chat. That conversation will be notably
less engaging.)

This tool is equipped with Dave's codeFreshener.

Further notes for those who care:


Jabber-RPC
-=-=-=-=-=-

(This is a summary of a document available in the tool's website.)

Last year, a specification for Jabber-RPC was jointly developed by Dave
and several of the Jabber developers, which can be seen at
http://www.pipetree.com/jabber/jrpc.html .

This framework does *NOT* implement that specification.

It turns out that to my surprise the specification only handles
Jabber-user-to-Jabber-server XML-RPC. I don't even know of a server to
test that spec with. Instead, I have implemented a user-to-user RPC
mechanism, vastly more usable in the RU/Frontier environment. But that
implementation is not standardized by anyone except me. AFAIK, I'm the
first to do this.

(The specification for what I am doing is included in the Tool's website.)

*Jabber Accounts
-=-=-=-=-=-=-=-=-

Jabber implements a three-tiered identity system: Username, server, and
*resource*. With one username, on one server, an arbitrary number of
Jabber clients can connect, as long as they all have different resources.

Thus, as long as you have a Jabber acoount somewhere... anywhere... it
is not necessary to create a new account for the framework. Just change
user.jabber to the account's values (or always pass the values to
jabber.openConnection()), and you'll be fine.

On that topic, if you do not want to download this framework (perhaps
because you aren't a developer), but would like to see the framework in
action, send a message to Jeremy@.../RadioUserland, not
forgetting that /RadioUserland part! My copy of Radio Userland will
echo back your text, with a few slight alterations. ;-)



Let's have fun!