This is more of a request than a discussion.
To fully utilize the OO Model, A skeleton object model using an object manager can guarantee that each record in a table is read only one time per execution.
possibility, pro's and con's?
I have never even considered it and do not intend to use it either.
My apps are running on several nodes/server and the synchronization point is the transactional database. Just my thoughts...
I don't think I've seen such a requirement; typically each client would read the most recent data from the database. If needed within a single client, this isn't too hard to manage, usually by seeing if the application already knows the object is being edited and just focusing the window containing the object.
If you're concerned about data collisions, I'd implement optimistic concurrency. Add a timestamp column to the "main" record and compare it before you update; if they are different abort the transaction.
I'm not concerned about collision but network traffic.
I'm faced with an application that is supposed to run a database over the internet, And with the currently available resources a local (the LAN side) data access| business logic server with a skeleton objects will help a lot.
Copyright (c) Marimer LLC