| 72 | | === API design principles === |
| 73 | | By the end of the hackathon, we had identified the following RESTful API principles, but they will continue to be [https://www.nescent.org/wg_evoinfo/PhyloWS/REST#Principles developed elsewhere] |
| 74 | | * Stateless REST, no accumulate-and-fire |
| 75 | | * Architecture modeled as resources on which CRUD operations are performed |
| 76 | | * Use common HTTP methods (GET, PUT, POST, DELETE) |
| 77 | | * Describe RESTful API in WSDL 2.0 |
| 78 | | * Reuse prior art |
| 79 | | === URL API === |
| 80 | | We started to design a URL API (pathinfo + query strings) on the [https://www.nescent.org/wg_evoinfo/PhyloWS/REST NESCent Wiki] |
| | 72 | * '''API design principles''' - by the end of the hackathon, we had identified the following RESTful API principles, but they will continue to be [https://www.nescent.org/wg_evoinfo/PhyloWS/REST#Principles developed elsewhere]: |
| | 73 | * Stateless REST, no accumulate-and-fire |
| | 74 | * Architecture modeled as resources on which CRUD operations are performed |
| | 75 | * Use common HTTP methods (GET, PUT, POST, DELETE) |
| | 76 | * Describe RESTful API in WSDL 2.0 |
| | 77 | * Reuse prior art |
| | 78 | * '''URL API''' - We started to design a URL API (pathinfo + query strings) on the [https://www.nescent.org/wg_evoinfo/PhyloWS/REST NESCent Wiki] |
