Are you using the compjid option? Unless you have a custom component written to stand in front of the PyMSNt instances then you shouldn't be.
Basically just set the <jid/> option differently for each transport. --- James On 11/08/2006, at 7:38 AM, Gonzalo Barrio wrote: > I was using the 0.10 version and I have a cluster of 3 msn instances. > With the new pymsn the cluster functionality is not working I use > the same configuration under 0.10 and works, when I run the 0.11.1 > it logs as msn.domain.com not msn-1.domain.com and the rest (msn-2 > and msn-3) never can connect to the server. > > How is the cluster functionality now in 0.11.1 or 0.11.2.... ? > Thanks in advance. > > Gonzalo Barrio > > James Bunton wrote: >> I've merged some changes into trunk. >> >> Changes since 0.11.1: >> * Fix to the getAttribute exception >> * Use twistfix library for twisted compatibility. >> * Fixed licensing issues for the Debian packager. >> * Fixed an XDB hash problem. >> * Added python-imaging notes to docs >> >> I'm planning on releasing this in a week if nobody has any trouble >> with it. >> >> You can get a tarball from my website at http://delx.cjb.net/pymsnt >> >> If your svn checkout is still using svn:// URLs then you'll need >> to run this command first >> svn switch --relocate svn://delx.cjb.net/ http://delx.cjb.net/svn/ >> pymsnt/ >> >> Then run these >> svn switch http://delx.cjb.net/svn/pymsnt/trunk >> svn up >> >> This version has an up to date TODO list :) >> >> --- >> >> James >> _______________________________________________ >> 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
