Hi,
On Oct 26, 2006, at 2:40 PM, Brian Safford wrote:
On Thu, 2006-10-26 at 11:50 +0200, Norman Rasmussen wrote:
ummmm, it's what the python shelve rules are.... from
http://docs.python.org/lib/node328.html :
"""The shelve module does not support concurrent read/write access to
shelved objects. (Multiple simultaneous read accesses are safe.) When
a program has a shelf open for writing, no other program should have
it open for reading or writing. Unix file locking can be used to
solve
this, but this differs across Unix versions and requires knowledge
about the database implementation used."""
So basically, "no".
I have no practical python knowledge - is why I ask questions here :-)
Rather make a copy of the spool file and go from there. The extra
data might cause wierd conflicts, so maybe it's better to split the
file into multiple files based on your load balancing schema.
That whole idea of a load balancer is that a user could get
connected to
any one of the instances, so that user's data needs to be available to
*all* the transports.
The other transports use xml files or MySQL tables - any chance that
this one could do the same?
I'd love to be able to test this with Jabber XCP, but in order to
do so
it has to run multiple instances and share the data.
I've talked with Brian about this.
Norman, I didn't check but does pyYIMt use a different file/shelf for
each user?
The load balancer does guarantee that each JID will only be sent to a
single transport.
Best regards,
--
HIId: Pedro Melo
SMTP: [EMAIL PROTECTED]
XMPP: [EMAIL PROTECTED]
_______________________________________________
py-transports mailing list
[email protected]
http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
