FYI: For anyone attempting this, there's a larger peice of work in line for PyYIMt (to migrate to alternative database storage classes). If you're interested in doing the work, please contact me so that I can offer tips & tricks on how to do it (with the least amount of work required).
There is an existing patch that converts PyYIMt to use xdb storage (like the other transports), but doesn't maintain backwards compatibility, so I can't apply it to CVS. On 3/22/07, Safford, Brian <[EMAIL PROTECTED]> wrote: > I don't know Python at all, but need to develop a utility that will take > N number of the PyYIMt user.dbm files and merge them into a new dbm file > that contains the most recent record for each user. > > First question is whether this is possible - is there timestamp > information in the user.dbm file that would allow a decision to be made? > > I'm currently running multiple PyYIMt gateways using separate user.dbm > files, but users that get connected to an instance for which they > haven't yet registered forces them to register. > > I'd like to run this utility on a periodic basis ( nightly, when the > gateways are stopped ) to help level the field. > > Thoughts? -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ _______________________________________________ py-transports mailing list py-transports@blathersource.org http://lists.modevia.com/cgi-bin/mailman/listinfo/py-transports
