[JDEV] Pooled users/groups?

[Peter Millard]

Yeah, a component is definitely the way to go... This way, everyone who
wants to potentially get messages would just register with this agent.

You could also do something for "broadcast" style lists in a similar manner,
just send out the msgs to everyone registered w/ that component.

Peter M.


----- Original Message -----
From: "Brian Lalor" <blalor at hcirisc.cs.binghamton.edu>
To: <jdev at jabber.org>
Sent: Wednesday, November 07, 2001 2:38 PM
Subject: Re: [JDEV] Pooled users/groups?


> I may have a solution, and I don't even think it will require that much
> coding.  It should be fairly trivial to set up a component/transport that
> would be able to handle this.  If a component is set up with the id
> "pool.hostname", then it will receive requests for anything at pool.hostname.
> anything could be the pooled group and will act like a gateway'd (like
> AIM) user and can have presence.  It would be up to the component to
> handle the routing of messages to individual JIDs.
>
> Damn, Jabber is so cool!  I discovered that this is possible thanks to DJ
> and mallum and the wonderful jabberpy <http://sf.net/projects/jabberpy/>
> which has component support in CVS.
>
> If I get around to implementing this, I'll throw it back to the community.
>
> B
>
>
____________________________________________________________________________
_
> B r i a n  L a l o r
blalor at hcirisc.cs.binghamton.edu
> http://hcirisc.cs.binghamton.edu/~blalor     Spam me not.
>    To get my pgp key, put "get pgp key" in the subject of your message
>
> ech`echo xiun|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol
>
>
>
>
>
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
>