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 works already. Still what's lacking
is an implementation of a client context in anything but Java. This
is the biggest challenge.
So if there is an interest in the community to write clients in .NET,
PHP, Ruby, Python, (or maybe JavaScript/AJAX???), etc., let's do it.
A full implementation would have to mirror "cayenne-client-
nodeps.jar", but it can start small, by providing only query API, and
then grow to support relationships and updates.
Thoughts? Comments? Volunteers? ;-)
Andrus
On Jul 5, 2006, at 11:46 AM, Tomi NA wrote:
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 not to have a number of templates, each
generating client code for a specific language, so that both Java
programmers and .net programmers could use the same
jetty/tomcat/whatever powered web service as a nice wrapper arround
the database?
Forgive me if I sound so 1999, but there still exist people like me
who have never written a WS so I have to ask. :)
t.n.a.
