[ome-devel] C/C++ client library for OME::Remote

[Chris Allan]

On Mon, Jul 12, 2004 at 06:15:46PM -0500, Curtis Rueden wrote:
> Hi Zach,
> 
> We are working on an OMECA-XML reader and writer, and are approaching these issues from the other direction. That is, we decided to write the reader/writer in Java, and then use the Java Invocation API ("reverse" JNI) to call the Java methods from C++ using JVM.DLL.
> 
> You could call the OME Remote Framework Java API using the same technique from your C++ application. Sun has some documentation online at:
>    http://java.sun.com/j2se/1.4.2/docs/guide/jni/spec/invocation.html
> 
> Cheers,
> -Curtis
> 
> At 03:50 PM 7/12/2004, Zachary Pincus wrote:
> >Hello,
> >
> >I've been looking into using the OME::Remote framework in one of my projects. However, since most of my code is C++ glued together with python, the existing Java client library doesn't appear to be of direct use to me.
> >
> >As such, I might be looking into implementing an XML-RPC client library for OME in C/C++ so that it could be SWIG-wrapped and used from any language. (a) Would this be useful to others? If so, I'll spend extra time on portability and unit tests... (b) Is this a tremendous undertaking, or something that could be accomplished (given the Java version as a guide) pretty easily? (c) Would it be a good idea to simply ape the existing Java interface/implementation, or is that something of a moving target?
> >
> >Any thoughts about the advisability/utility of such an endeavor would be appreciated.

Quite obviously, assuming the point of the XML-RPC client library was to
provide an API more suitable for language bindings, C is the best
option. This makes bindings for C#, Python, Perl, Ruby, etc. very
do-able.

In my personal opinion, JNI would be a huge hack for you.

> >
> >
> >Thanks,
> >
> >Zach Pincus

Ciao.

-Chris