--- In [email protected], Tom Chiverton <[EMAIL PROTECTED]> wrote: > Thought-making, certainly :-) Suppose I was using FDS, so I've got lots of client-side logic for what can and can't be changed. I then have to duplicate that all server-side as well, because I don't trust the client. That's just as much work as *not* using FDS, isn't it ? <
How you partition the application logic is orthogonal to the use of FDMS. FDMS should be employed when an application needs some or all of the following functionality: - the ability to edit/revert data locally - submit client changes in batches - survive network outages, i.e. changes can be made on the client while disconnected - data conflict notification and resolution - updates need to be replicated on (pushed to) multiple clients - fail over/clustering -- 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/
