our current api separate different functions through different url. It could be more simplicity and data-model oriented. In general, we have two layers apis. The first one works on the low level raw data which provides CURD operations, collect, read, update and delete. The second one works on the higher level analytic level, which provides aggregate metrics. By understanding above, I propose the following url style. It is heavily influenced by RESTful style, therefore will be more easy and compatiable for us to develop client App throught existed framework
linux-colonel
commented
11 years ago
our current api separate different functions through different url. It could be more simplicity and data-model oriented. In general, we have two layers apis. The first one works on the low level raw data which provides CURD operations, collect, read, update and delete. The second one works on the higher level analytic level, which provides aggregate metrics. By understanding above, I propose the following url style. It is heavily influenced by RESTful style, therefore will be more easy and compatiable for us to develop client App throught existed framework
POST /collect->POST /dataGET /query->GET /dataPOST /modify->PUT /dataPOST /delete->DELETE /dataGET /metrics->GET /metricsPOST /metrics->POST /metrics