Re: Update view of database on multiple web clients
- From: Roedy Green <my_email_is_posted_on_my_website@xxxxxxxxxxxxxx>
- Date: Tue, 28 Feb 2006 18:09:12 GMT
On Tue, 28 Feb 2006 16:40:38 GMT, David Segall <david@xxxxxxxxxxx>
wrote, quoted or indirectly quoted someone who said :
If two users
happen to update the field at the same time the second users version
will also prevail but the first user must be given the chance to see
it and complain about it.
Given subnanosecond clocks in CPUs, there is no chance of two updates
being simultaneous. You have to define a band of time by which YOU
means simultaneous, for which this evasive action gets invoked.
It would work like this. When you update, you timestamp with the
update. Before you update you look at the timestamp. if it was > X
seconds ago, you go ahead with the update. Otherwise do your evasion
thing, letting a user update his own change without debate, if there
has not been recent debate.
--
Canadian Mind Products, Roedy Green.
http://mindprod.com Java custom programming, consulting and coaching.
.
- References:
- Update view of database on multiple web clients
- From: David Segall
- Re: Update view of database on multiple web clients
- From: Rhino
- Re: Update view of database on multiple web clients
- From: David Segall
- Update view of database on multiple web clients
- Prev by Date: TOMCAT access across network
- Next by Date: Re: Are javac -target and -source arguments broken in JDK 1.5 ?
- Previous by thread: Re: Update view of database on multiple web clients
- Next by thread: Re: Update view of database on multiple web clients
- Index(es):
Relevant Pages
|
