31,029
edits
Google Summer of Code Ideas 2013: Difference between revisions
Jump to navigation
Jump to search
→link= Idea 1 : REST interfaces/API
| Line 44: | Line 44: | ||
== [[File:art.png|link=]] Idea 1 : REST interfaces/API == | == [[File:art.png|link=]] Idea 1 : REST interfaces/API == | ||
{{GSOCIdea| | {{GSOCIdea | ||
title= | |title=REST interfaces/API | ||
|briefexplanation=Develop a system to provides APIs using REST protocol. | |||
|knowledge=Eclipse + GIT + [http://en.wikipedia.org/wiki/REST REST protocol] + PHP 5.3+ | |||
|mentor=[[Laurent Destailleur]] | |||
|backup_mentor=to define | |||
|why=Be more ready to cloud or mobile usage that need such API (preferred to SOAP) to exchange data. | |||
|expexted_results=Having 100% of services actually covered by SOAP, covered by REST, including REST unit tests. | |||
|difficulty=Medium | |||
|risk=Low | |||
|more=All main elementsof Dolibarr must have a REST API to offer CRUD services (Create/Read/Update/Delete). | |||
All main elementsof Dolibarr must have a REST API to offer CRUD services (Create/Read/Update/Delete). | |||
List of elements to support are: | List of elements to support are: | ||
- Invoices | - Invoices | ||
| Line 68: | Line 64: | ||
- Agenda events | - Agenda events | ||
We recommand building first a generator to generate API from classes of elements. | We recommand building first a generator to generate API from classes of elements. | ||
}} | |||
Students already interested in working on this task: | Students already interested in working on this task: | ||