On 8/29/06, Brian Safford <[EMAIL PROTECTED]> wrote: > Before I attempt to get the yahoo-transport-0.3 running as well I > thought I'd ask the list to see if there is anyone else out there who > has successfully implemented it with Jabber Inc.'s server?
If you can, please use the CVS version. If you have issues, contact me, and I'll try walk you through them. I've never been able to test the transport with the commercial server, so this will be a first I think. -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ From [EMAIL PROTECTED] Tue Aug 29 11:44:20 2006 From: [EMAIL PROTECTED] (Norman Rasmussen) Date: Tue Aug 29 11:44:26 2006 Subject: [py-transports] Yahoo transport eats 100% cpu In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> On 8/28/06, Joe Moschetti <[EMAIL PROTECTED]> wrote: > The Yahoo transport seems to be eating 100% cpu constantly. Suggestions? Which version are you using? I'm trying to track down this frigging bug, but it's incredibly hard to reproduce the situation. -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ From [EMAIL PROTECTED] Tue Aug 29 11:50:19 2006 From: [EMAIL PROTECTED] (Norman Rasmussen) Date: Tue Aug 29 11:50:24 2006 Subject: [py-transports] problem with yahoo-transport In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> On 8/14/06, James Townson <[EMAIL PROTECTED]> wrote: > I've been having this problem for a long ago. > like two months ago, I tried yahoo-transport-2.3.2. so I got this > from=" yahoo.tjcn-linux" did that space appear during mail transit, or was it there in the xml stream? > message, now I tried yahoo-transport-3.0, I still got this old familiar > message. > I tried the transport with wildfire and ejabberd. What stanza did you send to the transport to cause it to reply with the one you posted? Which client are you using? -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ From [EMAIL PROTECTED] Tue Aug 29 11:52:20 2006 From: [EMAIL PROTECTED] (Norman Rasmussen) Date: Tue Aug 29 11:52:25 2006 Subject: [py-transports] Yahoo Transport In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> On 8/23/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I'm using PyMSNt, PyICQt, PyAIMt and PyYIMt transports and SMACK API to > register > them. > And it works fine for ALL transports but, although WITH YAHOO TRANSPORT THE > REGISTER IS OK, I get this exception (only with yahoo) Which version of the yahoo transport? Can you post some of the xml generated by the registration process. My guess is the yahoo transport is doing something slightly different. -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ From [EMAIL PROTECTED] Tue Aug 29 11:57:40 2006 From: [EMAIL PROTECTED] (Norman Rasmussen) Date: Tue Aug 29 11:57:56 2006 Subject: [py-transports] Jabber transparent to MSN and parameter questions In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> On 8/19/06, Bearcat M. Sandor <[EMAIL PROTECTED]> wrote: > I'm not *quite* sure what this transports are supposed to do. I have a jabber > server set up and the username i have for myself is > [EMAIL PROTECTED] I had hoped that the transports would allow > msn users to enter [EMAIL PROTECTED] in their msn clients and > contact me. This along with the aim and yahoo transports would reduce my IM > IDs to just one. Is that correct? Not really. The way is: You sign into the transport with your existing MSN address. Then msn users can chat to you as if you were on the MSN network. If you create a passport with the same address, then technically you have 'one' address to give to everyone. > Secondly, i'm a little unsure about how the jid and host parameters work. My > jabber server is on jabber.feline-soul.net. Does that mean i want the jid to > be "jabber" and the host to be "feline-soul.net"? jid needs to be the jid of the transport. so it needs to be something like 'msn.jabber.feline-soul.net' or if you wanted to make it private (so other servers can't use the transport), you can make it just 'msn' or 'msn.localhost'. host needs to be the public IP address, or DNS name of the machine if you want to support file transfers. This is told to the other client, so that it can send the file to the right place. btw: why don't you make your jid [EMAIL PROTECTED], that way your email address would match your jid. -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ From [EMAIL PROTECTED] Tue Aug 29 11:58:02 2006 From: [EMAIL PROTECTED] (Joe Moschetti) Date: Tue Aug 29 11:58:12 2006 Subject: [py-transports] Yahoo transport eats 100% cpu In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> CVS from August 24 or 25ish. 2006/8/29, Norman Rasmussen <[EMAIL PROTECTED]>: > > On 8/28/06, Joe Moschetti <[EMAIL PROTECTED]> wrote: > > The Yahoo transport seems to be eating 100% cpu constantly. Suggestions? > > Which version are you using? I'm trying to track down this frigging > bug, but it's incredibly hard to reproduce the situation. > > -- > - Norman Rasmussen > - Email: [EMAIL PROTECTED] > - Home page: http://norman.rasmussen.co.za/ > _______________________________________________ > py-transports mailing list > [email protected] > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports > -- Joe Moschetti http://jmoschetti45.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://modevia.com/pipermail/py-transports/attachments/20060829/25cbad41/attachment.htm From [EMAIL PROTECTED] Tue Aug 29 12:08:39 2006 From: [EMAIL PROTECTED] (Norman Rasmussen) Date: Tue Aug 29 12:08:55 2006 Subject: [py-transports] Yahoo transport eats 100% cpu In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> On 8/29/06, Joe Moschetti <[EMAIL PROTECTED]> wrote: > CVS from August 24 or 25ish. what's in yahoo-transport/CVS/Entries? -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ From [EMAIL PROTECTED] Tue Aug 29 13:11:57 2006 From: [EMAIL PROTECTED] (Daniel Henninger) Date: Tue Aug 29 13:11:21 2006 Subject: [py-transports] Yahoo contacts in Google Talk... In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> > On 8/26/06, Daniel Henninger <[EMAIL PROTECTED]> wrote: >> How odd. I rarely have problems with PyYIMt and PyIRCt. The only >> problems I've run into is that they tend to go byebye on me if the >> server goes away. (the other Pys keep trying to reconnect) > > yea, this was a tricky decision. Should the transport shutdown if it > can't contact the server? and for which reasons: connection refused, > connection accepted, but protocol error (wrong port, etc), wrong > password (do some servers return this when restarting?) > > Also the logic must be different at transport startup and during > reconnection. At startup, the jabber server might be slower starting > than the transport, so the transport should wait for it - for how > long? And during a reconnection - was there a good reason why we got > disconnected from the server? (Was it just restarting, or has it died, > what if it _then_ tells us we have the wrong password?) > > Maybe the logic needs to be changed, to keep trying (on start up and > reconnect), unless the server tells us - wrong password, conflict, or > protocol error:(bad-format, bad-namespace-prefix, invalid-xml, > restricted-xml, unsupported-encoding, xml-not-well-formed). (rfc3920, > section 4.7.3 is pretty comprehensive)? Generally I prefer that the transport keep trying to reconnect. Of course, that means that PyAIM/ICQ/MSNt run into the opposite problem. If there's a configuration error they try over and over and over again with no hope of success. (I've fielded quite a few questions due to this) I think some middle ground would be ideal. I definitely run into the issue where my server is starting up slower than the transports. Of course, PyICQ doesn't seem to be handling this situation well either. It doesn't die, but it also doesn't reconnect in a proper manner. I have to manually kick it in the ass. It -does-, however, manage to reconnect just fine i fthe server just flat out booted it's connection for some reason. Not entirely sure why one works and one doesn't. There's also functionality in the twisted Pys to have the transport probe everyone who's registered to relogin anyone who's still connected in jabber land. Works out well for a crash. Daniel > > -- > - Norman Rasmussen > - Email: [EMAIL PROTECTED] > - Home page: http://norman.rasmussen.co.za/ > _______________________________________________ > py-transports mailing list > [email protected] > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
