4:44 p.m.
Howdy!
As we discussed on our team meeting today, having basic query and pagination support would
be cool.
Here are some suggestions, gathered from previous conversations around the topic, and from
some BaaS providers in the wild.
Paging:
1) /cars/?limit=10&offset=3
2) /cars/?limit=10&skip=3
Query:
1) /cars/query?color=blue
2) /cars/?query={"color":"red",
"owner":"summers"}
3) /cars/?where={"brand":"BMW"}
4) /cars/?query={"engine":{"cylinders": 8}}
5) /cars/?query={"engine":{"cylinders":{"$gt":6}}}
This is not set into stone, just ideas, and I do think that anything above exact matches
should go after 1.0
Thoughts?
-- qmx
4:53 p.m.
Hello!
On Tue, Oct 30, 2012 at 10:44 PM, Douglas Campos <qmx(a)qmx.me> wrote:
Howdy!
As we discussed on our team meeting today, having basic query and pagination support
would be cool.
Here are some suggestions, gathered from previous conversations around the topic, and
from some BaaS providers in the wild.
Paging:
1) /cars/?limit=10&offset=3
2) /cars/?limit=10&skip=3
Query:
1) /cars/query?color=blue
2) /cars/?query={"color":"red",
"owner":"summers"}
3) /cars/?where={"brand":"BMW"}
4) /cars/?query={"engine":{"cylinders": 8}}
5) /cars/?query={"engine":{"cylinders":{"$gt":6}}}
This is not set into stone, just ideas,
I guess it's a matter of agreeing :) the main work is on the "ag
server component".
Question.... do we want to keep it flexible? E.g. if AG clients are
used for a backend that does not use "limit" for the pagination?
(I guess kinda similar to what we have on the endpoints, where you can
override the default)
and I do think that anything above exact matches should go after 1.0
fine w/ me
-M
Thoughts?
-- qmx
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
7:44 a.m.
On Oct 30, 2012, at 5:53 PM, Matthias Wessendorf wrote:
Hello!
On Tue, Oct 30, 2012 at 10:44 PM, Douglas Campos <qmx(a)qmx.me> wrote:
> Howdy!
>
> As we discussed on our team meeting today, having basic query and pagination support
would be cool.
>
> Here are some suggestions, gathered from previous conversations around the topic, and
from some BaaS providers in the wild.
>
> Paging:
>
> 1) /cars/?limit=10&offset=3
> 2) /cars/?limit=10&skip=3
Is the skip the number of pages, or the literal item count to start on?
Also, we would want a way to get back a total #, and page #'s give a page size. This
may be a separate call - wdyt?
>
> Query:
>
> 1) /cars/query?color=blue
> 2) /cars/?query={"color":"red",
"owner":"summers"}
> 3) /cars/?where={"brand":"BMW"}
> 4) /cars/?query={"engine":{"cylinders": 8}}
> 5) /cars/?query={"engine":{"cylinders":{"$gt":6}}}
>
> This is not set into stone, just ideas,
I guess it's a matter of agreeing :) the main work is on the "ag
server component".
Question.... do we want to keep it flexible? E.g. if AG clients are
used for a backend that does not use "limit" for the pagination?
(I guess kinda similar to what we have on the endpoints, where you can
override the default)
Where would you override this? In the pipeline creation?
Also, and opinions on using matrix parameters instead of query parameters? For now we
would need to combine with #PathParam & PathSegments. See
http://docs.jboss.org/resteasy/docs/3.0-beta-1/userguide/html_single/inde...
for details.
This would allow future nesting of queries.
> and I do think that anything above exact matches should go after 1.0
fine w/ me
+1
-M
>
> Thoughts?
>
> -- qmx
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
8:46 a.m.
The way github does paging looks nice,
http://developer.github.com/v3/#pagination
On Oct 31, 2012, at 8:44 AM, Jay Balunas <jbalunas(a)redhat.com> wrote:
On Oct 30, 2012, at 5:53 PM, Matthias Wessendorf wrote:
> Hello!
>
>
> On Tue, Oct 30, 2012 at 10:44 PM, Douglas Campos <qmx(a)qmx.me> wrote:
>> Howdy!
>>
>> As we discussed on our team meeting today, having basic query and pagination
support would be cool.
>>
>> Here are some suggestions, gathered from previous conversations around the topic,
and from some BaaS providers in the wild.
>>
>> Paging:
>>
>> 1) /cars/?limit=10&offset=3
>> 2) /cars/?limit=10&skip=3
Is the skip the number of pages, or the literal item count to start on?
Also, we would want a way to get back a total #, and page #'s give a page size. This
may be a separate call - wdyt?
>>
>> Query:
>>
>> 1) /cars/query?color=blue
>> 2) /cars/?query={"color":"red",
"owner":"summers"}
>> 3) /cars/?where={"brand":"BMW"}
>> 4) /cars/?query={"engine":{"cylinders": 8}}
>> 5) /cars/?query={"engine":{"cylinders":{"$gt":6}}}
>>
>> This is not set into stone, just ideas,
>
> I guess it's a matter of agreeing :) the main work is on the "ag
> server component".
>
> Question.... do we want to keep it flexible? E.g. if AG clients are
> used for a backend that does not use "limit" for the pagination?
> (I guess kinda similar to what we have on the endpoints, where you can
> override the default)
>
Where would you override this? In the pipeline creation?
Also, and opinions on using matrix parameters instead of query parameters? For now we
would need to combine with #PathParam & PathSegments. See
http://docs.jboss.org/resteasy/docs/3.0-beta-1/userguide/html_single/inde...
for details.
This would allow future nesting of queries.
>
>> and I do think that anything above exact matches should go after 1.0
>
> fine w/ me
+1
>
> -M
>
>>
>> Thoughts?
>>
>> -- qmx
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
10:50 a.m.
that is a nice document
thx for sharing
-M
On Wed, Oct 31, 2012 at 2:46 PM, Lucas Holmquist <lholmqui(a)redhat.com> wrote:
The way github does paging looks nice,
http://developer.github.com/v3/#pagination
On Oct 31, 2012, at 8:44 AM, Jay Balunas <jbalunas(a)redhat.com> wrote:
On Oct 30, 2012, at 5:53 PM, Matthias Wessendorf wrote:
Hello!
On Tue, Oct 30, 2012 at 10:44 PM, Douglas Campos <qmx(a)qmx.me> wrote:
Howdy!
As we discussed on our team meeting today, having basic query and pagination
support would be cool.
Here are some suggestions, gathered from previous conversations around the
topic, and from some BaaS providers in the wild.
Paging:
1) /cars/?limit=10&offset=3
2) /cars/?limit=10&skip=3
Is the skip the number of pages, or the literal item count to start on?
Also, we would want a way to get back a total #, and page #'s give a page
size. This may be a separate call - wdyt?
Query:
1) /cars/query?color=blue
2) /cars/?query={"color":"red",
"owner":"summers"}
3) /cars/?where={"brand":"BMW"}
4) /cars/?query={"engine":{"cylinders": 8}}
5) /cars/?query={"engine":{"cylinders":{"$gt":6}}}
This is not set into stone, just ideas,
I guess it's a matter of agreeing :) the main work is on the "ag
server component".
Question.... do we want to keep it flexible? E.g. if AG clients are
used for a backend that does not use "limit" for the pagination?
(I guess kinda similar to what we have on the endpoints, where you can
override the default)
Where would you override this? In the pipeline creation?
Also, and opinions on using matrix parameters instead of query parameters?
For now we would need to combine with #PathParam & PathSegments. See
http://docs.jboss.org/resteasy/docs/3.0-beta-1/userguide/html_single/inde...
for details.
This would allow future nesting of queries.
and I do think that anything above exact matches should go after 1.0
fine w/ me
+1
-M
Thoughts?
-- qmx
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
4:07 a.m.
Hi,
We have started to look into AEROGEAR-645 "Add Query/Paging support on
RESTful endpoints" and tried to gather there requirements from this thread
here:
https://gist.github.com/4147473
Please let us know if you are missing anything, or if there are additional
things to consider.
Thanks,
/Dan
--
View this message in context:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Query-Paging-Brain...
Sent from the aerogear-dev mailing list archive at Nabble.com.
8:46 a.m.
Overall looks good Daniel and I'd say go for it!
--
"The measure of a man is what he does with power" - Plato
-
@abstractj
-
Volenti Nihil Difficile
On Monday, November 26, 2012 at 8:07 AM, danielbevenius wrote:
Hi,
We have started to look into AEROGEAR-645 "Add Query/Paging support on
RESTful endpoints" and tried to gather there requirements from this thread
here:
https://gist.github.com/4147473
Please let us know if you are missing anything, or if there are additional
things to consider.
Thanks,
/Dan
--
View this message in context:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Query-Paging-Brain...
Sent from the aerogear-dev mailing list archive at Nabble.com (http://Nabble.com).
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org (mailto:aerogear-dev@lists.jboss.org)
https://lists.jboss.org/mailman/listinfo/aerogear-dev
12:53 p.m.
Thanks Bruno!
I was just wondering if you saw my question at the bottom of the page there:
Since AeroGear Controller does not currently handle RESTful services
neither paging of querying makes sense, which is leaving me a little
puzzled as to what the task at hand should actually do?
Should I go ahead with this and stash it in a branch until we add support
for RESTful endpoint?
On 26 November 2012 15:46, Bruno Oliveira <bruno(a)abstractj.org> wrote:
Overall looks good Daniel and I'd say go for it!
--
"The measure of a man is what he does with power" - Plato
-
@abstractj
-
Volenti Nihil Difficile
On Monday, November 26, 2012 at 8:07 AM, danielbevenius wrote:
> Hi,
>
> We have started to look into AEROGEAR-645 "Add Query/Paging support on
> RESTful endpoints" and tried to gather there requirements from this
thread
> here:
> https://gist.github.com/4147473
>
> Please let us know if you are missing anything, or if there are
additional
> things to consider.
>
> Thanks,
>
> /Dan
>
>
>
> --
> View this message in context:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Query-Paging-Brain...
> Sent from the aerogear-dev mailing list archive at Nabble.com (
http://Nabble.com).
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org (mailto:aerogear-dev@lists.jboss.org)
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
1:48 p.m.
Sorry Daniel, just missed that. Maybe qmx has more thoughts on it and we can discuss at
the meeting tomorrow.
Could we do something using Resteasy or JAX-RS? I know that it will add more dependencies
to controller, but maybe could help us to design our RESTful API while we figure out how
to do it on top of Resteasy.
I'd say, go for it and we can definitely create a new branch if you want. I'm +1
to move forward.
Any thoughts guys?
--
"The measure of a man is what he does with power" - Plato
-
@abstractj
-
Volenti Nihil Difficile
On Monday, November 26, 2012 at 4:53 PM, Daniel Bevenius wrote:
Thanks Bruno!
I was just wondering if you saw my question at the bottom of the page there:
Since AeroGear Controller does not currently handle RESTful services neither paging of
querying makes sense, which is leaving me a little puzzled as to what the task at hand
should actually do?
Should I go ahead with this and stash it in a branch until we add support for RESTful
endpoint?
On 26 November 2012 15:46, Bruno Oliveira <bruno(a)abstractj.org
(mailto:bruno@abstractj.org)> wrote:
> Overall looks good Daniel and I'd say go for it!
>
>
> --
> "The measure of a man is what he does with power" - Plato
> -
> @abstractj
> -
> Volenti Nihil Difficile
>
>
>
> On Monday, November 26, 2012 at 8:07 AM, danielbevenius wrote:
>
> > Hi,
> >
> > We have started to look into AEROGEAR-645 "Add Query/Paging support on
> > RESTful endpoints" and tried to gather there requirements from this
thread
> > here:
> > https://gist.github.com/4147473
> >
> > Please let us know if you are missing anything, or if there are additional
> > things to consider.
> >
> > Thanks,
> >
> > /Dan
> >
> >
> >
> > --
> > View this message in context:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Query-Paging-Brain...
> > Sent from the aerogear-dev mailing list archive at Nabble.com
(http://Nabble.com) (http://Nabble.com).
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev(a)lists.jboss.org (mailto:aerogear-dev@lists.jboss.org)
(mailto:aerogear-dev@lists.jboss.org)
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org (mailto:aerogear-dev@lists.jboss.org)
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org (mailto:aerogear-dev@lists.jboss.org)
https://lists.jboss.org/mailman/listinfo/aerogear-dev
1:13 a.m.
Sounds good, lets discuss this at the meeting today.
On 26 November 2012 20:48, Bruno Oliveira <bruno(a)abstractj.org> wrote:
Sorry Daniel, just missed that. Maybe qmx has more thoughts on it and
we
can discuss at the meeting tomorrow.
Could we do something using Resteasy or JAX-RS? I know that it will add
more dependencies to controller, but maybe could help us to design our
RESTful API while we figure out how to do it on top of Resteasy.
I'd say, go for it and we can definitely create a new branch if you want.
I'm +1 to move forward.
Any thoughts guys?
--
"The measure of a man is what he does with power" - Plato
-
@abstractj
-
Volenti Nihil Difficile
On Monday, November 26, 2012 at 4:53 PM, Daniel Bevenius wrote:
> Thanks Bruno!
>
> I was just wondering if you saw my question at the bottom of the page
there:
> Since AeroGear Controller does not currently handle RESTful services
neither paging of querying makes sense, which is leaving me a little
puzzled as to what the task at hand should actually do?
>
> Should I go ahead with this and stash it in a branch until we add
support for RESTful endpoint?
>
>
>
>
> On 26 November 2012 15:46, Bruno Oliveira <bruno(a)abstractj.org (mailto:
bruno(a)abstractj.org)> wrote:
> > Overall looks good Daniel and I'd say go for it!
> >
> >
> > --
> > "The measure of a man is what he does with power" - Plato
> > -
> > @abstractj
> > -
> > Volenti Nihil Difficile
> >
> >
> >
> > On Monday, November 26, 2012 at 8:07 AM, danielbevenius wrote:
> >
> > > Hi,
> > >
> > > We have started to look into AEROGEAR-645 "Add Query/Paging support
on
> > > RESTful endpoints" and tried to gather there requirements from this
thread
> > > here:
> > > https://gist.github.com/4147473
> > >
> > > Please let us know if you are missing anything, or if there are
additional
> > > things to consider.
> > >
> > > Thanks,
> > >
> > > /Dan
> > >
> > >
> > >
> > > --
> > > View this message in context:
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Query-Paging-Brain...
> > > Sent from the aerogear-dev mailing list archive at Nabble.com (
http://Nabble.com) (http://Nabble.com).
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev(a)lists.jboss.org (mailto:aerogear-dev@lists.jboss.org)
(mailto:aerogear-dev@lists.jboss.org)
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev(a)lists.jboss.org (mailto:aerogear-dev@lists.jboss.org)
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org (mailto:aerogear-dev@lists.jboss.org)
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
4397
days inactive
4425
days old
9 comments
7 participants
participants (7)
-
Bruno Oliveira -
Daniel Bevenius -
danielbevenius
-
Douglas Campos -
Jay Balunas -
Lucas Holmquist -
Matthias Wessendorf