[JDEV] Feature question

[Ryan Eatmon]

No that's not what I'm looking for.  What I'm looking for is a way to
have the server know that jabber id "jabber:bob at jabber.org" is really
"jabber:vila at jabber.org".  So that all things sent to
"jabber:bob at jabber.org" are instead delivered to
"jabber:vila at jabber.org".

That way I can tell one of the daemons that they are the acting master
and they tell the jabber server that they want to login in as
"daemon1234", but they are also listening to "daemonMaster".  Then all
messages sent to "daemonMaster" will handled by "daemon1234".  

I've done this using a forwarding client listening to "daemonMaster"
that looks for an X tag in my namespace that tells who sent the
message.  "daemonMaster" then takes the same message and ships it out to
"daemon1234".  "daemon1234" has to parse the X tag and look for my
forwarding tag to see who to send the reply to.  This is not a good
solution, but it works for now.

Other uses for this include a Help Desk organization where they have a
"Help Desk" id and various people monitor it at different times.  The
person who is supposed to be monitoring it tells the server that "Help
Desk" is now aliased to "Ryan Eatmon" and the server sends all messages
to "Help Desk" to "Ryan Eatmon" instead.  There can be lots of uses for
this feature.

You could even have it so that you can alias multiple ids to one id and
then round robin the messages to the various ids that it receives.  This
way you could write a distributed client that has ten daemons listening
on one address.  Or ten help desk employees listening to one Jabber
address.

-- 

Ryan Eatmon                reatmon at ti.com
-----------------------------------------
Mixed Signal Product Development EDA Team