;quota_info": { ...}
> > }
> >
> > The user can choose between query parameters vs json body as they please,
> > and we still have a single specification of the request.
> >
> > On Thu, Jan 14, 2016 at 10:09 AM, Alex Rukletsov
> > wrote:
> >
> > > Fo
cation of the request.
>
> On Thu, Jan 14, 2016 at 10:09 AM, Alex Rukletsov
> wrote:
>
> > Folks,
> >
> > I would like to gather your opinions about a concern related to operator
> > HTTP endpoints. From one side we agreed that for simplicity and
> consistency
>
please,
and we still have a single specification of the request.
On Thu, Jan 14, 2016 at 10:09 AM, Alex Rukletsov
wrote:
> Folks,
>
> I would like to gather your opinions about a concern related to operator
> HTTP endpoints. From one side we agreed that for simplicity and consistency
> we s
of that one - @Vinod may
> be able to chime in).
>
> Thanks for getting the conversation started!
>
> --
> *Marco Massenzio*
> http://codetrips.com
>
> On Thu, Jan 14, 2016 at 11:09 AM, Alex Rukletsov
> wrote:
>
> > Folks,
> >
> > I would like t
le to chime in).
Thanks for getting the conversation started!
--
*Marco Massenzio*
http://codetrips.com
On Thu, Jan 14, 2016 at 11:09 AM, Alex Rukletsov
wrote:
> Folks,
>
> I would like to gather your opinions about a concern related to operator
> HTTP endpoints. From one side w
Folks,
I would like to gather your opinions about a concern related to operator
HTTP endpoints. From one side we agreed that for simplicity and consistency
we should bake all request data in a single JSON. From the other side, some
parameters, like a force flag, do not really belong to request
