Most of the traffic conversation here seems to revolve around applications
that are essentially read-only or are behaving as though they are single
user.

Any tips and tricks to be found regarding the synchronisation of data in a
multi-user application involving a database.

For example (since hotel booking is a prominent example in the RIA world),
lets suppose I have two customers (Customer A and Cust B) trying to book the
same hotel room on the same day. Both see it as free in the RIA, Cust A
books it and now the other must know about it too, so effectively then
that's a straight refresh of Cust B display and the aborting of the booking
in progress.

Lets suppose my application allows Cust B to mark several days of room
bookings and (s)he has to hit 'book now' to commit to the booking. While
this is going on 'Cust A' has booked one of those days, so now I must merge
the updated database with the on-screen representation, so it's no longer a
straight replacement of the application display from the database, we're
having to merge.

Perhaps I'd best not even mention database locking and handling that in a
RIA.

Get the idea? I appreciate this isn't entirely Flex specific.

If there are tips and tricks/best practices in this area with regard to
Flex, I'd like to know about them before I re-invent the wheel!

Paul




--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/flexcoders/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/flexcoders/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[EMAIL PROTECTED] 
    mailto:[EMAIL PROTECTED]

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 



Reply via email to