--- 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 the application logic is partitioned is orthogonal to the use of FDMS. If your application needs some or all of the following features you should consider using FDMS: - ability to edit/revert changes locally - ability to send changes in a batch - ability to perform edits when disconnected from remote destination - ability to perform conflict detection/notification and resolution - ability to replicate changes across multiple clients - ability to cluster services and provide fail over -- 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/
