I am curious about one thing..how does a client hold information that
another client may need to access, for a long period of time? My
understanding of EJB, and in general access to resources via web apps is
that a client submits a form or hits a link that goes to the server. The
server does its thing as quickly as possible and returns a response. Even if
the user has accessed a bean and stored an HttpSession reference to it..does
that put a lock on the row in the database? I would believe using stateless
EJB bean would solve this problem..not sure about stateful.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> [EMAIL PROTECTED]
> Sent: Friday, December 01, 2000 1:32 AM
> To: Orion-Interest
> Subject: SV: What is the best way to "select for update" ?
>
>
> Use optimistic locking..
>
> All updated data gets a timestamp and all retrieved data keeps the
> timestamp....Before update compare the timestamp, if its a match noone has
> done an update. If it dont match you should refuse the update and give the
> user a message about this.
>
> Problems with webbrowsers are many, and the worst is that you can never
> depend on the browser or whatever is within to participate in a
> transaction
> (since the browser fetch and forget..)
>
> Klaus
>
> -----Opprinnelig melding-----
> Fra: Keith Kwiatek [mailto:[EMAIL PROTECTED]]
> Sendt: 30. november 2000 23:37
> Til: Orion-Interest
> Emne: What is the best way to "select for update" ?
>
>
> Hello,
>
> Just wondering how/if orion/ejb makes it possible for a web client to
> "select data for update" in such a way that another web client
> will receive
> a notice if it trys to fetch the same data (possibly for
> update).... I know
> that orion/ejb handles short term transactions, but what about where a
> client hold data (that another client may want to access) for long periods
> of time, --how do you handle this via orion/ejb?
>
> Thanks,
> Keith
>
