Re: Using WO with multiple users.

[Alexander Lamb <lamba@acm.org>]

Well, the locking strategies you mention are all implemented and
available with WebObjects (EOF actually).
By default, the optimistic locking is used.

For more information you may read "Locking and update strategies" in the
Enterprise Objects Framework developpers guide, page 217 (assuming you
are using WOF4).

There are not so many differences from developping a traditional
client-server app. Actually the locking strategy is more of a semantic
problem (e.g what are you trying to achieve with your app).

Alexander Lamb
Apple Enterprise Software & Services
Geneva / Switzerland

IDfusion wrote:
> 
> I want to create an application where multiple users can access, view
> and modify the database all at once. With other applications you must
> use some sort of locking mechanism to ensure the state of the database
> is not comprimised. I want to start tackling this with WebObjects and
> Oracle. Would anyone be able to give me an idea as to where to start?
> What are my choices for locking mechanisms (optimistic, pessimistic,
> etc...) I am using Java with WO and any examples, which I can not find,
> would be very helpfull. I've never developped a multiple user
> application with a web based tool and am unsure as the differences from
> that to a desktop (Networked) application.
> 
> Thank Robert
> 
> Happy New Year.