Naw, jabberd2 should work just fine. =) Just a matter of configuration. [Twisted is, unfortunately, a mobile target for us. James put in a twistfix thing into pymsnt that I need to incorporate into pyaim/pyicq. Hell, pyaim and pyicq need some love and a new release anyway]
Daniel On Aug 31, 2006, at 2:44 PM, Joe Berry wrote: > Thanks for all the advice. I will do some more testing tonight. > As aim > support is important to me, do you think it makes sense to consider an > alternative jabber server, such as ejabberd? > > Joe > >> On 8/31/06, Daniel Henninger <[EMAIL PROTECTED]> wrote: >>> One other thing you might want to make sure you don't have enabled >>> is... useRouteWrap. That should not be turned on if SASL is turned >>> on for Jabberd2. >> >> You, mean it _should_ be on right? I've been happily running with >> saslUsername, useComponentBinding, and useRouteWrap all enabled - >> that >> was until twistd 2.4 came along. >> >>> [One thing I wanted to do at some point is see if I can't get the >>> transports to detect what they've connected to.. like "oh hey, you >>> are jabberd2, i'm turning on this and that". Who knows how possible >>> that is ;D ] >> >> mmm, might be able to based on 'for server x use mode y', but that >> would suck. Idealy in the *cough* near future, there should only be >> _one_ preferred way of connecting a component. Obviously JEP-0114 >> will have to be supported as a 'legacy' mode, but this new hodge >> podge >> of jabberd2/wildfire/sasl mess should go away. >> >> -- >> - 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 >> > > > _______________________________________________ > py-transports mailing list > [email protected] > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
