Concurrency should be addressed by design. Can we let SUN put synchronization on every class because of the exeption in my ASO?
Also your sequencing will cause other issues, make users feel your site is weird. For example, at one page, the user use the File/New Window in IE to open a window and submit a transaction, the transaction may take a while, the user goes back to the first page to sumbit another transaction. You will block the transaction since the other transaction is running? I will be very unpleased if I were the user. On 6/7/06, Henri Dupre <[EMAIL PROTECTED]> wrote:
why would you let a single user with one session object execute concurrent requests? that can cause a lot of funky behavior IMO unless you took it into account in your design (I'd be curious to know how many developers are writing synchronization code to their ASOs)... I've seen concurrency exceptions on ArrayList iterators happening because of the same object being modified by two concurrent requests. On a low load, you are probably very unlikely to see that type of behavior but the more users you have the more this can happen. Also queuing concurrent requests can help to lower the load of a server http://www.onjava.com/pub/a/onjava/2004/03/24/loadcontrol.html On 6/7/06, Cliff Zhao <[EMAIL PROTECTED]> wrote: > > Not a good reason to put synchronization on requests. > > On 6/6/06, Henri Dupre < [EMAIL PROTECTED]> wrote: > > > > On 6/6/06, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > > > > > > Why? > > > > > > Simply to prevent invalid things happening when two pages are modifying > at > > the same time the same ASOs. > > I see tons of reasons to prevent that... Writing ASO synchronization by > > hand > > is quite a pain. > > > > Thanks, > > > > Henri. > > > > > > -- Thanks, Henri.
