Having spent about 10 minutes looking at the yahoo-transport code, it seems to me that there might be a pretty simple way to get it to support multiple instances while using the dbm file methods. Here are my thoughts:
A config file element is added that indicates where the base directory is for the individual user .xml files, similar to how PyAIM/ICQ/MSN work. Each time the transport starts, it empties the user.dbm file that 'spool' points to, and as users connect, the individual user .xml file is opened and the contents transferred to the associated entry in the user.dbm file. Time passes ... When users disconnect, their individual entry is written back to disk, and a flag is set in the user.dbm entry to reflect that fact so that when the transport exits it only has to write the entries that haven't previously been written. Thoughts? Regards, Brian On Thu, 2006-10-26 at 18:05 +0100, Pedro Melo wrote: > Hi, > > On Oct 26, 2006, at 4:32 PM, Norman Rasmussen wrote: > > > On 10/26/06, Pedro Melo <[EMAIL PROTECTED]> wrote: > >> Norman, I didn't check but does pyYIMt use a different file/shelf for > >> each user? > > > > nope, all users in the same file. > > Ok, this is the deal breaker. > > >> The load balancer does guarantee that each JID will only be sent to a > >> single transport. > > > > that's cool then. Just extract the correct users to the correct > > file :-) > > I see what you want to do, and it would work OK for most of the time. > > But users are reshuffled when you add or remove an instance of pyYIMt. > > 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 _______________________________________________ py-transports mailing list [email protected] http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
