Object Middleware for
CMS
This project is continuing, and we intend to generalize our
system to include not only SQL result sets, but arbitrary object
collections. Our overall design goals, some of which were mentioned
earlier, include:
-
DB vendor abstraction.
-
Language natural access: STL for C++, RMI for Java,
...
-
Location transparency - client code does not have to know
whether an object has been transferred in order to call a method on that
object.
-
Front-end caching - client code will cache frequently
accessed result sets to minimize latencies
-
integrated security and firewall transversal - currently
GAE uses CLARENS for rpc and security functionality. Utilize
CORBA, DCOM, UDDI as well.
-
Random access of rows in result set - reordering of
transfers to meet user's requests. If a user jumps to row 10,000
of the result set, then intervening rows need not be transferred before
row 10,000 can be transferred.
-
Eliminate latencies associated with packaging result sets
to files by streaming directly to the client.
-
Self describing object collections
Next> |