esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ethan Jewett <>
Subject Re: API2 - response format changes - request for input
Date Tue, 03 Nov 2009 13:20:33 GMT

The changes are only to the /api2/ endpoint and I'm being careful not
to change the existing API. There are now two files in my local
checkout because I am reimplementing the XMLApiHelper trait, so that
file will show up in the next patch.

I'm also fairly certain that no one is currently developing any
clients based on the new API, but I did have a discussion about it on
Twitter with Daniel (I think), so I just want to make it clear on the
list that while this API is available, it is not stable. If you're
using it (and I'd appreciate people trying to use it and giving
feedback), you should probably make clear what you're doing on the
list so that we can coordinate..

With regards to examples: Absolutely, we need them on the wiki if
people are going to be able to implement against this in a sane way.
Currently I am documenting URLs, methods, and parameters, but I'll
start to document response formats as well as soon as they start to
stabilize. Thanks for the suggestion :-)


On Tue, Nov 3, 2009 at 4:51 AM, Richard Hirsch <> wrote:
> It might also be useful to have examples from the various API calls in
> the wiki so that users can get a feel for the data structures.
> D.
> On Tue, Nov 3, 2009 at 8:53 AM, Markus Kohler <> wrote:
>> Hi all,
>> Will take a look at this later today.
>> Markus
>> On Nov 3, 2009 6:02 AM, "Richard Hirsch" <> wrote:
>> Are the breaking changes just in the API2.scala code or in other scala
>> classes as well.
>> Since I don't think anyone has built any clients using the new API, I
>> don't think we should have any problems.
>> I'm glad to see any changes that make the API more REST-like (be it
>> using tags instead of attributes, etc.) inasmuch as I'm not a REST
>> expert, I'll leave you to judge whether the changes are appropriate or
>> not.  Maybe, you could reach out to others on twitter with more REST
>> experience and ask them.
>> D.
>> On Mon, Nov 2, 2009 at 9:16 PM, Ethan Jewett <> wrote: >
>> All, > > This email is h...

View raw message