-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Everyone,
Okay.. I have a question. I think (perhaps wrongly but) that most
people are using SQLObject in a web fashion these days. To my limited
sight, the code seems structured to exist in a more non-web fashion.
What do I mean by this ?
*) There is writeLocks - surely not required since most frameworks
run the entire thread under a transaction anyway. Surely these are
therefore, at best, depreciated in a web environment and, at worst,
obsolete. It also makes pickle hard (obviously) cause I have to remove
them from the object before storing into memcache and then assign a
new one after a 'get' (of course, I have to do this with sqlmeta
- -anyway-, but at least I can see the reason d'etre with that. very
handy and cool)
*) cache built in at a fundamental level - most web people would
probably feel safer with memcache, currently I don't see anyway to
disable this other than by hacking the get method inside SQLObject to
not put items into it's cache (at least, that's the way I got memcache
to be used and the inbuilt cache never used). Yes, I -can- subclass
the object, but surely the base object should be 'light' and then a
new SQLObject with caching derives from that. This would mean anyone
could subclass from the base object and the FK/Join goodness without
being forced to use SQLObjects caching.
*) no query caching - seems strange to have object caching but no
query caching, when query caching is generally where 'web' starts to
notice major slowness. I have created a simple queryCache using a
global inside the servlet/framework request to do this, and it seems
to work pretty fine.
*) connection pooling - I would have thought (again perhaps
naively) that in a web environment, this should exist outside the ORM.
In essence, something like pgpool-II or sequoia. There are whole
applications designed to do this, and even at it's best, on a page
load I notice that there are about 20 connections (did I mention that
the pages in my website/environment can get pretty Object-Heavy ? :).
So, is it insanity to propose that perhaps there is a
sqlobject-web version ? missing writelocks (acid handled by the
database), no caching built in (memcache), no connection pooling
(again, other parts of the framework can handle this and argueably
better/cleaner).
This email should NOT be taken as flamebait or anger or anything
other than a progressive/open email to start a discussion. If anyone
takes any offense, then my deepest apologies, as none are meant in anyway.
Regards
Stef
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJhgrqANG7uQ+9D9URAppvAJwKZFTB9QVp0BnTPIlJphj2PUweLgCgizgO
lt4o6qgrjgPBvmLICavJsk4=
=xYqf
-----END PGP SIGNATURE-----
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
sqlobject-discuss mailing list
sqlobject-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
