On 2/18/06, Ralph Meijer <[EMAIL PROTECTED]> wrote: > On Tue, Jan 24, 2006 at 04:04:40PM +0200, Norman Rasmussen wrote: > > On 1/24/06, Jacek Konieczny <[EMAIL PROTECTED]> wrote: > > > Things that need to be solved: > > > > > > 1. redirecting SPPS queries addressed to users to the external > > > component. > > > 2. providing the external component with roster information. > > > > The way I see it, by the time you've written code (for each server) to > > 'filter' out those pubsub packets and send them to the pubsub > > component, you might as well have added spps directly to the server. > > > > It saves having to write the roster sharing code too. The only other > > reason I can think of why you'd want to 'share your roster' is if you > > want multiple identity jids under a single account. (i.e. > > meta-accounts). > > I think that jabberd 2 has another component protocol that would allow > this. You can route stanzas according to the namespace of the child of > iqs. I haven't had the time to try that out, though.
It doesn't help with disco items though, as those are in the disco namespace which used for other things as well - I think. You'd have to make the PEP component handle _all_ disco registrations and requests - which isn't terrible I guess. The only jabberd2 component spec that I know of is [1], and it doesn't seem to indicate that it can handle binding to xml subdomains. Of course, the spec doesn't have to match the code currently implemented. [1] http://jabberd.jabberstudio.org/dev/docs/component.shtml -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/
