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

[Zachary Pincus]

Hmm, I seem to have touched on something here. Seems such a library 
could be useful.

As one grad student, I can't do a whole lot big-picture-wise, but I am 
still interested in working on a C/C++ XML-RPC client implementation.

If I could solicit some advice to get started:
(1) Should I start out by simply aping the Java client library, or 
would there be a better approach? (Start by producing a WSDL and 
implement a client compliant with that?) Realistically, the only thing 
I can do alone is to replicate what the Java can do. If others want to 
help, the scope could be expanded...
(2) How much of a moving target are these APIs, etc? Should I hold off 
for a while before trying to write a portable client library?
(3a) How do people feel about JNI? Sure, writing a C interface that 
calls the Java on the back-end, and is called by Perl/Python/&c. on the 
front end is a huge and ridiculous hack, but it might be quicker and at 
least the client codebase is unified...
(3b) Would C be substantially better than C++, language-binding-wise? 
(SWIG does fine with clean C++, but I'm not sure about bindings to C#, 
or anything else not covered by SWIG. Plus it's hard to call C++ from 
C, but that's probably not a huge problem, is it?)

Any thoughts, advice, et al. would be appreciated,

Zach



On Jul 13, 2004, at 6:50 AM, Harry Hochheiser wrote:

>
> Stefan:
>
> I agree completely - WSDL's would be a great idea. As the API is still 
> evolving, any such definitions might still present a moving target, 
> but providing this sort of access should be on the agenda.
>
> -harry
>
> On Jul 13, 2004, at 8:28 AM, Stefan Frank wrote:
>
>> Couldn't agree more: I think the goal has to be, to have a complete 
>> Webservice-Api that covers querying for Images, Datasets etc, allows 
>> Remote Annotation for Ressources(picking up on Ilya's Ideas: This 
>> allows to distribute the processing of Images to remote-machines): 
>> But do we have documentation on the Webservices?! Are there any 
>> wsdl's out there, that describe the Remote-Api? Can we somehow ensure 
>> at least some WS-I-compliance to be sure that we don't loose any 
>> clients on the way(Let me add some more "ugly" clients like LabView, 
>> which uses .net for Webservices)? Only one language-binding (to Java) 
>> is not sufficient for most enviroments...
>>
>> cheers
>> stefan
>>
>>
>
>
>
> Harry Hochheiser, Ph.D.
> Image Informatics and Computational Biology Unit
> Laboratory of Genetics
> NIH, National Institute on Aging
> 333 Cassell Drive
> Suite 3000
> Baltimore MD 21224
> 410 558 8046
>
> _______________________________________________
> ome-devel mailing list
> ome-devel at lists.openmicroscopy.org.uk
> http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel
>