[OTDev] Compound API
Nina Jeliazkova nina at acad.bgFri Nov 6 12:54:13 CET 2009
- Previous message: [OTDev] Compound API
- Next message: [OTDev] Compound API
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Egon, Egon Willighagen wrote: > Hi Christoph, > > On Fri, Nov 6, 2009 at 11:09 AM, Christoph Helma <helma at in-silico.de> wrote: > >> Lets start with an easy one: >> http://opentox.org/dev/apis/api-1.1/structure >> > > I do not have overly much experience with REST service details, but > how do the services handle MIME types? That is, how do I specify what > mime type I'd like to see returned? Does the OpenTox API support the > Accepts: HTTP header [0]? > Yes, HTTP Accept header is supported by all services. > A second question... is anyone already working on a newBSD/MIT/LGPL > licensed Java libary for OpenTox API clients? > AFAIK, not at this moment, since we are heavily on the design phase still. But Ambit is LGPL licensed and it will make sense at certain point to clean up dependencies and split the REST related code into a separate project. > Finally, I would suggest JSON to be added to the list of (optional) > output formats, which makes it easy to use the OpenTox API from > JavaScript libraries... > > Should be fine as optional format. BTW, could you recommend any of the existing Javascript libraries ? Best regards, Nina > Egon > > 0.http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html > >
- Previous message: [OTDev] Compound API
- Next message: [OTDev] Compound API
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Development mailing list