|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Rickard �berg
|Sent: Sunday, November 19, 2000 11:23 PM
|To: jBoss Developer
|Subject: Re: [jBoss-Dev] Instance cache and commit option c
|
|
|marc fleury wrote:
|> I sort of believe there is an interesting RO policy at the container as
|> well. It won't cover the "direct DB access" but will speed up
|the container
|> level... see my previous mail.
|
|If I understand you correctly you are talking about using RO flags to
|allow multiple threads in one entity instance. We have that today, but
|it is a proprietary flag with counter-spec workings useful for
|perfomance reasons.
|
|However, in this discussion we should talk about an optimistic
|concurrency control scheme that *is* spec-compliant, i.e. work with
|multiple concurrent entity instances mapped to the same key.
true good point
|
|> |concurrency control by reading the data outside of the transaction
|> |and re-reading it in the transaction before writing it--first validating
|> |that it has not been changed. You can use a token (e.g. last
|> |modified number or date) to do this, although a more general
|>
|> :))) this is pretty much the "pattern from the server side".
|
|Except the database would be doing it. The TSS.com pattern is done by
|the application developer. So, either db or app, not container in any
|case.
well the container would need to add the field we were talking about etc
etc...
ok listen no biggie we will deal with it when we deal with it.
marc
|
|/Rickard
|
|--
|Rickard �berg
|
|Email: [EMAIL PROTECTED]
|http://www.telkel.com
|http://www.jboss.org
|http://www.dreambean.com
|
|
