I think "remoting" nails what it does better than anything else. Even
though the heavy lifting is done by the OPP and "remoting" is just a
small part of it, making OPP interfaces work across the wire, average
user will not (and should not) care about OPP. What's important is
that you can write an application that supports unforeseen data
queries and persistence life-cycle.
Also note that outside of the tier directly connected to the DB,
"object/relational" term is not applicable.
So how about "Remote Object Persistence" then? A user definition may
go like that:
... "Remote Object Persistence" a low-overhead web services-based
technology that provides lightweight and generic object persistence
and data query functionality to 'remote' applications. It consists of
Cayenne web service (CWS) and Java client library ...
Andrus
This archive was generated by hypermail 2.0.0 : Fri Nov 11 2005 - 08:01:33 EST