multimediapress wrote:
Hi,
It works. Great support!
great!
Regarding DevForce we are just in the early stages of the evaluation yet (mainly on paper specs). What attracted us to it is how the n-tier model seems to be handled (poorly connected/disconnected client managment, ability to do rich query against the cache on the client). However, we are new to O/RM problematic so it's likely that we are misundestanding some aspects or misevaluating the respective impact of those aspects.
that's indeed a big problem but it has a wide range of 'solutions' which all are not really great. The biggest problem you've to solve is 'what is my 'truth', the real data?'. Because if Client A modifies data locally and client B who has connection to the service, alters the same data centrally, what happens when A wants to sync the changes? This might sound easy to solve, till you realize that A might have made other changes based on the changes made earlier, which make it very difficult to reject A's earlier changes, so B's changes are overwritten, otherwise all changes made by A locally can be tossed away.
Sometimes this is solved by a local database which is then synced using synchronization services, e.g. locally a SqlCE database is used and centrally a normal sqlserver database. You can achieve that with Adapter and our system. You're using mysql, so you can use a local mysql database, and switch between which system to use by switching the connection string for example, however you still have to sync the data, which is the cumbersome part. I'm not sure if devforce has solved this properly, as there is no real solution to this: they all suck in one way or the other as syncing offline data with online databases always requires the removal of some changes made already.