[ome-devel] Existing client side code in C

[Harry Hochheiser]

Josh:

I did not see any other comments on this, so I'll jump in...

I think a simple interface of the form that you're suggesting seems 
quite reasonable and straightforward, but i have to wonder about doing 
it over straight HTTP.  Given that we've got the XMLRPC interface - 
which is not going away any time soon - maybe it would make sense to 
wrap these simple calls in XMLRPC..

why bother? Well, this would simplify the configuration and operation 
on the other side,  as they could be handled by the same code that does 
the existing XMLRPC.

Of course, the problem with this is that code would have to change if 
XML-RPC was changed by something else.. which brings us  back to the 
discussion of XMLRPC vs.  SOAP or whatever else.  I don't expect that 
we'll resolve this any time soon, but maintaining two parallel yet 
separate access approaches (XML-encoded vs. straight HTTP) seems 
sub-optimal..

any other comments?
-harry

On Aug 11, 2004, at 10:25 AM, Joshua Moore wrote:

> I'd like to throw a few cents into the "thin layer" idea proposed early
> on, but with a twist.
>
> Currently, OME-IS works with simple GET statements like:
>
>    GET http://ome.../cgi-bin/omeis/Method=GetThumb&PixelsID=39
>
> Perhaps we can take this simplicity, add a few extensions, and have a
> working REST web service (thereby sidestepping the XML-RPC/SOAP
> discussion) for OME-DS. What we'd propose is to provide addressable
> locations for each SemanticType. There are a couple of ways of doing
> this. E.g.
>
>    GET http://ome...:8080/Attributes/Images/Dimensions/X?PixelsID=39
>
> .......
> thoughts?
> - josh.
>