Board index » delphi » OPF, Caches and concurrency
Hechicero
Delphi Developer |
OPF, Caches and concurrency2004-07-01 02:08:59 AM delphi108 Hi, Sorry for the long post I am begining to design a next proprotype of my opf and I have to make a decision regarding its architecture. The OPF has cahes for the clean objects and caches for the dirty objects in a transaction. We plan to separate a serve and a client. The server holds the OPF and all the objects (something like an object enviroment) and the clients access the objects remotelly. We want the clients to use the objects as if they where local.... like.. Customer := RemoteFactory .CreateNewCustomer; ... use customer as it is a local object De design will address concurrency. This are the posibilities I have in mind a) Remote Proxys Where every message to an objects (method invocation, property read, etc) will be translated to a message through the net (LAN, less probable internet). The client only have this proxys and the factory to generate instances. Right know we have a code generation that could generate the proxys manually. Adv) Proxys can be in any language, can generate then automatically, light clients, can implement observers on objecs in server, etc Disadv) Net Traffic. ( This is my personal and theorical favorite, but performance is very important) b) Copy of the object in the client Under this schema, the server would only hold clean objects and clients shoud have dirty ones. This wold require to add some functionallity to clients and they wont be thin and they will be in delphi. c) Hibrid Proxys A remote proxys that holds all messages sent to an objects and send them all toghether to the clients d) No server, just tymestamps. e) Servers exposes services but not objects. Server could export soap function and procedures. Clients would call those functions insteas of creating objects. This are the designs in the top of the list. I will really appreciate your comments and experience in the subject. If some data is missing please ask. Esteban Calabria |