Pavel, Current API was developed long time ago and was not actively developed. It may looks inconsistent for some use cases. May be it is a good idea to develop new API and deprecate current.
>From my experience we should take care: 1) "null" cache names 2) some commands could have state, for example large SQL query that could be fetched page by page 3) It will be "nice to have" to be able to run all command from browser address line. On Mon, Jun 20, 2016 at 8:59 PM, Pavel Tupitsyn <ptupit...@apache.org> wrote: > Igniters, > > There are two serious issues with current Ignite REST API: > > 1) It does not care about HTTP verbs (GET/POST/etc). > GET must never modify anything, for example (because GET requests can be > cached, duplicated, etc). > > 2) Proper resource paths are not used > For example, to get a cache value, instead of > GET /ignite?cmd=get&key=myKey&cacheName=partionedCache > it should be > GET /ignite/caches/partitionedCache/keys/myKey/ > > Modify cache key: > PUT /ignite/caches/partitionedCache/keys/myKey/ > DELETE /ignite/caches/partitionedCache/keys/myKey/ > > > I think we should deprecate current API and provide a new one that follows > the guidelines. > A good writeup on a proper REST API design can be found there: > https://zalando.github.io/restful-api-guidelines/ > > > Thoughts, comments? > > Pavel. > -- Alexey Kuznetsov GridGain Systems www.gridgain.com
