Greg Stark <gsstark@xxxxxxx> writes:
> Jan Wieck <JanWieck@xxxxxxxxx> writes:
>
>> Even applications that have statefull enduser terminals (like SAP R/3 for
>> example) never allow an open transaction over user interaction.
>
> I'm not sure using SAP as your paragon of design excellence is a wise choice
> here. From what I understand SAP implemented its own locking system because
> the database it was based on didn't offer any locking at all.
>
> But your basic point is sound. For a web site I would definitely avoid using
> anything like database locks and even avoid doing anything with application
> locks if possible.
Well, I don't necessarily have to use locks. I want any form of
concurrency control that ensures serializability. Optimistic
approaches would be fine as well.
> If you really really want to expose the database session state I think he's on
> the right track using SQLRelay. This would let him handle reconnecting a user
> with her session even if she's connecting to a different Apache process.
But why should I have SQLRelay between me and the database?
I don't plan to use any of its "real" features. It would just be a
proxy with a known address that maintains a database connection.
Obviously, the database server itself has a known address and
maintains database connections...
Jens
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@xxxxxxxxxxxxxx)
|
