Difference between revisions of "REST abstraction for ECF"
m (→Primary goals)
|Line 78:||Line 78:|
=== Links ===
=== Links ===
Revision as of 16:47, 11 May 2009
Project Lead: Holger Staudacher (IRC: staudi)
Mentor: Scott Lewis, Marcelo Mayworm
This project is part of the Google Summer of Code 2009
Many service providers using a REST based API to offer developers access to their services, i.e. Twitter, Facebook and so on. The result of this is that some third parties provide Java based libraries, which covers this API's. The ECF team played a little bit with the Twitter API and use therefore a library called Twitter4J.
The disadvantage of this technique is a dependency to the third parties library. This means an ECF container based on such a library is dependent on the diversity of this. To decouple these dependencies an own ECF based REST abstraction should be created within this GSoC project.
- A full working API for the REST client side to communicate to any RESTful web service.
- Upgrading the Twitter Provider to use this REST API
Here is a complete list of the milestones and release candidates planned for this plugin.
|M1||June 16||Implementation of the ECF Remote Services API for REST|
|M2||June 28||Architecture for REST webservices (POST, GET, UPDATE, DELETE)|
|M3||July 15||Couple the abstraction layer with the remote service API implementation|
|M4||July 26||The resource representation concept|
|M5||July 31||Implementation of some resource representations (XML, RDF, HTML and so on)|
|RC1||August 4||Round up the API and writing documentation|
|RC2||August 8||Fix some bugs|
|Pencils down||August 11||-|
Getting the source
Do you have a great idea for the REST abstraction? Just open a new feature request.