Re: [ecf-dev] REST API M3(update)

[Scott Lewis <slewis@xxxxxxxxxxxxxxxxx>]

Hi Holger,

This sounds like terrific progress, and thanks very much for the 
notification.  I would encourage all SOC students to do similar 
notifications here as progress is made (i.e. solicit review and feedback 
not just from your mentor, but the entire ECF community...they are, 
after all, the ultimate target 'customer' for all such work :).

Holger...I will certainly review and provide feedback, but this week is 
busy for me (for reasons named after a famous astronomer, as well as 
reasons associated with a certain employer), so there may be a bit of a 
delay for my feedback.  I hope this won't slow you down.

I would ask that *anyone* that is interested in this work (as I hope 
several/many are) consider reviewing and commenting on it...assuming 
that's OK with Holger.  We want to give him the full open source 
experience for his soc project, after all, right?  :)  Also, the more 
diverse the input/feedback, the quicker the work will reach maturity, 
and the quicker it will be usable by the wider community.

RE: the question of adding an extension point or an osgi service...I 
would consider this your call (Holger)...and I think you should base it 
upon which mechanism(s) you are more interested in learning about...i.e. 
OSGi services or extension points.  My one thought is that it would be 
good to keep the dependencies down to a minimum for the API, just so 
everything is ultimately usable in as many runtime contexts as possible 
(i.e. small/device runtimes, servers, small servers, etc).

Thanks,

Scott


Holger Staudacher wrote:
> Hi all,
> today I have committed the M3 version of the REST API. The 
> implementation of the remote service api is now finished. Maybe 
> someone can review it?
> I have also implemented a generic test and a specific one for twitter, 
> see org.eclipse.ecf.test.remoteservice.rest.twitter.TwitterTest. You 
> can see the results at [1]. To get the source take a look at [2].
>
> I'm currently implementing a concept for rest resource 
> representations. This is one of the bigger parts of this API. Everyone 
> should be able to add own resource representations. So this sounds 
> like an extension point (or maybe an osgi service), what do you think? 
> The xml resource representation will be included in the API and a 
> seperate json implementation will be available in an extra bundle.
>
> If you are interested in the rest api, found a bug or just have some 
> ideas please feel free to file bugs. You can find the main task under 
> [3].
>
> Enjoy this early version and please provide feedback ;)
>
> Regards Holger
>
>
>
> [1] http://twitter.com/eclipsedummy
> [2] http://wiki.eclipse.org/REST_abstraction_for_ECF#Getting_the_source
> [3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=275722
>
> Innoopract Informationssysteme GmbH
> hstaudacher@xxxxxxxxxxxxxxxxx
> Tel: 0721 - 66 47 33 - 0
> Fax: 0721 - 66 47 33 29
> ========================= Legal Disclaimer =========================
> According to Section 80 of the German Corporation Act Innoopract
> Informationssysteme GmbH must indicate the following information:
> Address: Stephanienstrasse 20, 76133 Karlsruhe Germany
> General Manager: Jochen Krause
> Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883
> ====================================================================
>
> _______________________________________________
> ecf-dev mailing list
> ecf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ecf-dev