BTW, I was trying to jumpstart this discussion on the dev list in the
context of the related Summer of Code project:
http://objectstyle.org/cayenne/lists/cayenne-devel/2006/07/0019.html
We'll see if this generates wider interest.
Andrus
On Jul 7, 2006, at 4:06 AM, Tomi NA wrote:
On 7/5/06
On 7/5/06, Andrus Adamchik <[EMAIL PROTECTED]> wrote:
The interesting part is "processMessage(ClientMessage)" - essentially
all communications (including queries and updates) are done using a
set of ClientMessages. The simplest message would be a QueryMessage
that holds a NamedQuery. This is pro
Remote calls are done via a RemoteService interface (all low-level
details are handled by Hessian).
public interface RemoteService extends Remote {
RemoteSession establishSession() throws RemoteException;
RemoteSession establishSharedSession(String name) throws
RemoteException;
Ob
On 7/5/06, Andrus Adamchik <[EMAIL PROTECTED]> wrote:
Actually clients written in other languages is one area that has a
huge potential. And this is something I'd really like to explore.
Current transport layer (Hessian) has support in many other
languages, also a standard WS interface is being
Actually clients written in other languages is one area that has a
huge potential. And this is something I'd really like to explore.
Current transport layer (Hessian) has support in many other
languages, also a standard WS interface is being developed as a
Summer of Code project. All this w
It just occured to me that cayenne remote object persistence might be
the key to a level of interoperability that I need in a very, very
heterogenous environent (i.e. my office) where people use Java, .net
and php, depending on the project, programmer and legacy code.
Is there any special reason n
