[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cxs] Another productive Workgroup 3 session
Workgroup 2 just had a _very_ productive meeting (after som postponed ones) :-)
Interesting stuff to see from WG3 - and especially liked Serge’s touch at the end there! It seems brilliant. We have attempted to apply this in our work too.
While we’re at it we propose an even simpler DSL for the query, why not simply drop the whole “function” and “arguments” thing and just go for a function:[args] pattern?
This is basically the same, but leaner syntax!
BTW: Using functions to create the entire query language is supposedly used elsewhere too :-). I will try to get some links
Also, we have opinions on the following:
* We should not use POST for queries but GET, as this is much more obvious - cleanly using POST to create and GET to, well get data.
* We think the complex stuff (query, sorting?) modelled as JSON should be sent in the body (this is how Elasticsearch does it, and it looks nice)
* Simple parameters such as offset, pageSize and maybe parameters to return should be plainly sent in the querystring, so one can easily access data even without using the body parameter and complex JSON stuff?
Check out the swagger file for the /events/ api endpoint. (sorry, just committed, no pull req this time!)
Finally - we are very skeptical of a generic /query endpoint - we prefer that each endpoint (events/ profiles/ etc) rather enable passing a query object to them - so you will never have to worry about what will be returned and how to make it work.
Vennlig hilsen/Best regards