On 10/9/06, Michael Vogel <[EMAIL PROTECTED]> wrote:
> Norman Rasmussen schrieb:
> > I think this is the Yahoo network dropping the connection.
>
> Yeah I think this could be true. Yahoo isn't really stable and I don't
> mean your transport ;-) When I was using the original client it
> disconnects randomly as well.

cool, so nothing has regressed :-)

> > I've been
> > debating on whatever or not the transport (compare to the client)
> > should be responsible for initiating the reconnect - and making the
> > client do it, makes sure that nothing gets into a loop.
>
> I do understand the problem. I think the transport should have some
> reconnect option with a time out option. (Maybe reconnect only 10 times
> then pause for several minutes and so on)

Mmm, and if you log in with another yahoo client, then it should try at all :-)

> > The good news is that xmpp.py libs 0.4 rc tar.gz has been put
> > together, and should be out some time this week. After that a few
> > minor todo items on the transports, and they too get a release.
>
> That sounds fine. Do you have a changelog? I would like to know what
> changed since 0.3.

yep, it's in the .tar.gz

-- 
- Norman Rasmussen
 - Email: [EMAIL PROTECTED]
 - Home page: http://norman.rasmussen.co.za/
From [EMAIL PROTECTED]  Mon Oct  9 07:58:49 2006
From: [EMAIL PROTECTED] (Norman Rasmussen)
Date: Mon Oct  9 07:58:57 2006
Subject: [py-transports] yahoo-transport and Jabber XCP
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

On 10/9/06, Pedro Melo <[EMAIL PROTECTED]> wrote:
> >         connection =
> > xmpp.client.Component
> > (config.compjid,config.port,debug=debug,domains=
> > [config.compjid,config.confjid],sasl=sasl,bind=config.useComponentBind
> > ing,route=config.useRouteWrap)

does XCP useComponentBinding?

(trying to figure out if you need to change the compjid in the domains part too)

-- 
- Norman Rasmussen
 - Email: [EMAIL PROTECTED]
 - Home page: http://norman.rasmussen.co.za/
From [EMAIL PROTECTED]  Mon Oct  9 09:18:52 2006
From: [EMAIL PROTECTED] (Pedro Melo)
Date: Mon Oct  9 09:18:51 2006
Subject: [py-transports] yahoo-transport and Jabber XCP
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

Hi,

On Oct 9, 2006, at 8:58 AM, Norman Rasmussen wrote:

> On 10/9/06, Pedro Melo <[EMAIL PROTECTED]> wrote:
>> >         connection =
>> > xmpp.client.Component
>> > (config.compjid,config.port,debug=debug,domains=
>> >  
>> [config.compjid,config.confjid],sasl=sasl,bind=config.useComponentBin 
>> d
>> > ing,route=config.useRouteWrap)
>
> does XCP useComponentBinding?

Is this the Jabberd2.0 new protocolo for external componentes? If  
yes, then no. It does not.

Basically, XCP (at least version 4) requires a static configuration  
on the router side. It requires an ID for each component, that  
combined with a realm gives you the link name that external  
components must use to connect (thats what we use compjid for in  
pymsnt and now in the yahoo-transport). The hostname setup is a  
different configuration entirely.

So we need both: compjid for the name used in the initial <stream>  
handshake, and then hostname for the official name of the transport.


> (trying to figure out if you need to change the compjid in the  
> domains part too)

No. compjid is only used in the initial connection.

BTW, compjid is a valid JID also, so you can assume that stanzas  
addressed to it are valid stanzas if you feel like it. It would be  
nice that you do so.

One reason is this: if we get a lot of customers, we tend to start a  
special xmpp load balancer with the name yahoo.domain. This component  
only job is to route messages to several yahoo-transport instances  
named yahoo1, yahoo2, yahooN... On each instance, we set compjid to  
yahooX, and hostname to yahoo.domain. This way we get a cluster of  
yahoo transports all of them responding to the same domain. End-users  
don't even need to know that we use clustering of external components.

The reason to reply to compjid is related to monitoring and  
statistics. We use a XMPP-based bot that queries all our services  
using compjid to check out stats and availability. The ability to  
reply to an iq disco or jabber:iq:register or even ad-hoc commands  
over compjid is very useful in those situations, even if you only  
allow admin to use that address.

Best regards,
--
HIId: Pedro Melo
SMTP: [EMAIL PROTECTED]
XMPP: [EMAIL PROTECTED]

Reply via email to