[jdev] Re: Auto-configured external gateways

Norman Rasmussen normanr at gmail.com
Fri Aug 26 13:54:59 CDT 2005


I've been having at trying to get the yahoo-transport from the xmpp.py
project to work with this JEP....., here's my problem

Is <bind> in the root namespace?

for most componenents the default namespace is set to
jabber:component:accept, so this makes any bind calls occur in the
jabber:component:accept namespace too.

I'm trying to send (after the handshake, but before the disco results):

<bind from="transport.domain" name="transport.domain" id="1" />

is this too much? the server doesn't reply.... or is this because the
disco results have been asked for but not yet returned?

On 26/08/05, Daniel Henninger <jadestorm at nc.rr.com> wrote:
> And I could really care less what it is as long as it lets me indicate
> that I want to be multiple domains without making multiple connections.
> =D  What I'm going to do for now is instruct folk to set up aliases of
> some sort or "configure the gateway manually".  But I'm very interested in
> seeing this proceed and will likely join in on the discussion about how to
> handle it if there is some.  ;D
> 
> That said, why is it jabberd2 specific?  In the sense of, why can't that
> protocol more or less be made into a JEP as is?  Is there something wrong
> with their implementation that doesn't scale away from jabberd2?  It
> looked pretty simple and right to the point to me.
> 
> Daniel
> 
> --
> "The most addictive drug in the world is music."
>      - The Lost Boyz
> 
> > 2005/8/25, Stephen Marquard <scm at marquard.net>:
> >> Is anyone interested in this becoming a real JEP rather than j2 internal
> >> documentation, i.e. would it be worth the effort to submit it to the JEP
> >> process?
> >
> > The solution for getting a component to automatically work under more
> > than one hostname is some kind of <bind/>ing.
> >
> > But the jabberd2 component protocol is very much jabberd2 internals
> > specific and I would not like it to become "the standard" for
> > connecting components AS-IS.
> >
> > Jabberd2 specific things should be removed or generalised.
> >
> > --
> > smk
> > _______________________________________________
> > jdev mailing list
> > jdev at jabber.org
> > http://mail.jabber.org/mailman/listinfo/jdev
> >
> >
> >
> 
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mail.jabber.org/mailman/listinfo/jdev
> 


-- 
- Norman Rasmussen
 - Email: norman at rasmussen.co.za
 - Home page: http://norman.rasmussen.co.za/



More information about the JDev mailing list