NYCPHP Meetup

[Patrick May]

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.

~ p




On Mon, Jun 30, 2008 at 10:34 AM, Allen Shaw <ashaw at polymerdb.org> wrote:

> anoland at indigente.net wrote:
>
>> -----Original Message-----
>> From: Allen Shaw <ashaw at polymerdb.org>
>>
>>
>>> ... I need to provide several users with access to an online php/mysq
>>> database app, where the user's Internet connection is intermittently slow or
>>> down.  ...
>>>
>> I would research Google Gears and/or Firefox's Prism (or whatever is
>> finally got named). It would close the gap for the most part by making
>> syncronization easier.
>>
> Good idea.  Haven't dealt with those at all yet; sounds like a possibility.
>
> 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
>



-- 
Patrick May
135 Oak Street
New York, NY 11222
+1 (347) 232-5208
patrick at hexane.org
http://www.hexane.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nyphp.org/pipermail/talk/attachments/20080630/86bb0ac0/attachment.html>