Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "EGI AppDB REST API CHANGELOG"

From EGIWiki
Jump to navigation Jump to search
m
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[Category:Community Engagement ]]
===Introduction===
===Introduction===
The current document keep logs with changes between the versions of [[TNA3.4_Technical_Services#Applications_Database|AppDB]] REST API.
The current document keep logs with changes between the versions of [[TNA3.4_Technical_Services#Applications_Database|AppDB]] REST API.


==[[TNA3.4_AppDB_REST_API_v1.0|Version 1.0]] (TBA)==
==[[EGI_AppDB_REST_API_v1.0|Version 1.0]] (2012-06-28)==
* Authenticated write access through support of PUT/POST/DELETE HTTP verbs as per the CRUD paradigm.
* Authenticated write access through support of PUT/POST/DELETE HTTP verbs as per the CRUD paradigm.
* Backwards incompatible changes compared to v0.2. Please see the full [[EGI_AppDB_REST_API_v1.0| API Reference]] for details.
* Deprecated v0.2 of the API. It will still be available for a limited period of time, but will not be supported.
* Deprecated v0.2 of the API. It will still be available for a limited period of time, but will not be supported.
* Obsoleted v0.1 of the API. It will no longer be available.
* Obsoleted v0.1 of the API. It will no longer be available.

Latest revision as of 10:16, 20 December 2012

Introduction

The current document keep logs with changes between the versions of AppDB REST API.

Version 1.0 (2012-06-28)

  • Authenticated write access through support of PUT/POST/DELETE HTTP verbs as per the CRUD paradigm.
  • Backwards incompatible changes compared to v0.2. Please see the full API Reference for details.
  • Deprecated v0.2 of the API. It will still be available for a limited period of time, but will not be supported.
  • Obsoleted v0.1 of the API. It will no longer be available.

Version 0.2 (2011-12-01) deprecated

Version 0.1 (2011-03-07) obsoleted

  • Initial release of API