Patrick May wrote:
I would point out that:
1. Transactions will not be useful if you cannot connect to the database
2. Google Gears and Prism seem to focus first on bridging the web /
application space for a single user, rather than dealing with
multi-way synchronization
Source code control systems are explicitly designed to manage the
process of synchronizing local state with a repository in a controlled
fashion. Ultimately, if there is a conflict it's not just up to your
application to resolve, but also your users.
How do you prevent a room from being double booked? You can look at
booking patterns and develop an algorithm can be developed that
minimizes collisions. But who gets a room if it is double booked?
That's probably a phone call or a conversation between employees.
Hi Patrick,
Yes, you've summarized it perfectly. I was already thinking of version
control systems as a similar situation: the conflicts have to be
resolved by a human being who's aware of the real world situation. The
app just can't know which commit to take.
Thought it wouldn't hurt to ask for a magic bullet, but you're stating
what I figured already: this is application-specific and it's up to me
to program the collision detection and resolution methods.
Thanks,
Allen
--
Allen Shaw
slidePresenter (http://slides.sourceforge.net)
_______________________________________________
New York PHP Community Talk Mailing List
http://lists.nyphp.org/mailman/listinfo/talk
NYPHPCon 2006 Presentations Online
http://www.nyphpcon.com
Show Your Participation in New York PHP
http://www.nyphp.org/show_participation.php
