Hi. On 27.10.2005, at 19:37 Uhr, Wolfram Stebel wrote:
JMS was announced to be fast...
It is quite fast and I have noticed no slowdown in my apps. But updating the DB is only made by humans here ...
Data should be updated in the second application, so that a refresh in thebrowser will reflect the change... For now i have to re-login, thats semi-optimal.
Do you use the sessions default editing context with its default caching values (1 hour)? Perhaps just re-reading the value from the database when it is needed should do the trick?!
So, why turn optimistic locking into pessimistic?
Just handle the optimistic locking failures. cug
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
