That's fine, but is there a way to pass the new connection to the
Manager so that it uses that one and not the static one? I don't want
to have to drop SPOD to facilitate this. :-( The way I see it, the main
thread can continue using the static feature of neko.db.Manager, while
I'd like the updater thread to use a new seperate connection, while
still using neko.db.Manager.
Thanks,
Lee
Nicolas Cannasse wrote:
Okay, here's a question for you. I'm using SPOD, so both threads
initialize the neko.db.Manager class and pass the db connection
statically to that class. If all threads used by a single vm share the
same memory, then technically, use of the static features of Manager
would use the same data. Am I right? If so, then how do I split this
per thread?
You can define your own Connection by implementing the appropriate
methods of neko.db.Connection, that will perform the lock before each
access.
Nicolas
--
Neko : One VM to run them all
(http://nekovm.org)
