[Seaside] Seaside and GOODS

[Ramon Leon]

> Hey, do you have any experiences with Seaside, GOODS and 
> heavy traffic on the server?
> I hold a GOODS connection for every session and close it, 
> when the session is closed. However, it seems, that GOODS has 
> problems with concurrency. For example:
> 
> Client 1: read,     , change,       , commit
> Client 2:     , read,       , change,       , commit
> 
> This gives a KKCommitFailure at the second commit (i think). 
> Especially with BTrees and TSTrees this can be a huge 
> problem. How do other object oriented database solve this 
> locking and transaction things?
> 
> Regards,
> Martin

Isn't this exactly the expected behavior?  This is standard optimistic
locking, first commit wins, so where's the issue?

Ramon Leon
http://onsmalltalk.com