On 10/27/06, Brian Safford <[EMAIL PROTECTED]> wrote:
Your first response to my question suggested that the 'shelve' object doesn't handle concurrent read-write access, so it would seem to me that using it as you suggest below would be problematic.
I meant to word it as: let's build some back ends that work in the same way that the existing shelve data store does.
Could I suggest/recommend that you give some thought to moving the current data-access code to a new object so that folks can work on the other storage backends w/o having to mess with the core code?
Because of python's flexibility it's possible to do this without changing most of the existing code.
I can probably find some experienced Python programmers to help with this effort. We have about 80,000 Jabber users internally at EDS, and many of them really like to be able to chat with Yahoo users.
Cool! If you can link them up with me, I can provide a mentor framework to fast-track them with exactly what they need, etc. -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ _______________________________________________ py-transports mailing list [email protected] http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
