Op zaterdag 27 augustus 2005 04:42, schreef James Bunton: > As long as each session is handled by the same thread there shouldn't > be any trouble. > > What exactly are you splitting up into threads? From what I've heard > Python threading isn't really very good. The global interpreter lock > means only one python thread can run at a time. > > You may want to consider just running two Python processes, with some > kind of component in between to divide up requests between them. > > Eg, run a msn1.host and msn2.host, have msn.host do a round-robin > distribution. So user1 registers with msn.host and is always silently > redirected to msn1.host
Or make it really clusterable: for this you need to make sure that the database (accounts etc) is duplicated in all nodes runing PyMSNt. The Jabber server then needs to do the round-robin for the transport. In ejabberd this should be already possible: just add entries for each PyMSNt node in ejabberd's config file (this is what Alexey said me in the past). Could be useful: http://starship.python.net/crew/gandalf/PyErlang/ -- Mvg, Sander Devrieze. xmpp:[EMAIL PROTECTED] ( http://jabber.tk/ ) From [EMAIL PROTECTED] Sat Aug 27 06:19:47 2005 From: [EMAIL PROTECTED] (James Bunton) Date: Sat Aug 27 06:20:00 2005 Subject: [py-transports] PyMSNt patch for discovering adhoc commands In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> PyMSNt has this working now too :) --- James On 22/08/2005, at 10:24 PM, Norman Rasmussen wrote: > JEP-0050 states in section 2.2: > > If additional information about a command is desired, the requester > queries for disco information on the command node: > > <example 5 and 6> > > A responder MUST at least provide an appropriate <identity/> and > <feature var='http://jabber.org/protocol/commands'/>, and SHOULD > include <feature var='jabber:x:data'/>. It is not required to support > additional information about a command. If the command is not > available to the requester, the responder SHOULD respond with a 403 > "Forbidden" error. > > This patch [1] adds the #info feature:commands reply, (and a empy > #items reply). It missed the identity, but something is better than > nothing. > > [1] http://www.darkskies.za.net/~norman/jabber/pymsnt-adhoc-disco.patch > > In retrospect the disco framework needs to rather implement #info and > #items in a central class that deals with retrieving these values > transparently. The commands node should inherit from this class, and > the enumeration of commands should use the same functions that getting > the list of nodes uses (the xml is tit-for-tat in the end). For > operations such as set that invoke the actual commands, there could be > a method to override. > > -- > - Norman Rasmussen > - Email: [EMAIL PROTECTED] > - Home page: http://norman.rasmussen.co.za/ > _______________________________________________ > py-transports mailing list > py-transports@blathersource.org > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports >
