Hi
I'm still investigating about sqlobject integration in webware.
My concern is now about performance, and more precisely about db
connection management and webware multithreading.
I've seen no precise documantation about this.
To perform fast, db connections must remain persistent and be reused by
webware threads.
How does sqlObject perform in a threaded environment like webware?
I saw in the source that there is a connectionHub object.
Does this mean that I can safely use sqlObject without caring about db
connections?
The connectionHub object seems to store a connection per thread.
If it does not exist, it takes the hub.processConnection value.
So, if I understand well, I simply have to set sqlhub.processConnection
near my SQLObject declarations (directly in the module root), and
everything will run fast and smooth?
What if I restart the database (without restarting the appServer). Will
the connections restart automatically?
Webware has a package called dbutils that manages DB-API2 and PyGreSQL
connections efficiently:
this means that it can maintain a pool of reusable connections, and it
takes care of keeping them alive.
Do I need it?
Thanks for your help
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
sqlobject-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
