just been reading the draft rfc
i think a limit of pinned connections per fdo provider would be good
so you can not exhaust the number of available connections thru
pinned ones
"There are only three methods supporting transaction, ..."
explaining which ones aren't help paint the picture a bit
in a typical web app, the session which your example assumes
which is the expected norm for web developers, is that you would
use a transaction for
as such most web apps tend to only ever hold a transaction
for a request
consider the example
log in, pin an oracle connection, update one row, do nothing
would that create a db lock unless something else is done for 20 min?
sessions != requests
might need some sort of purge all pinned connections, as short
of a server restart, 20 mins is an outtage
z
--
Zac Spitzer -
http://zacster.blogspot.com+61 405 847 168
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
