<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 01/11/2013 11:55 AM, Douglas Campos
wrote:<br>
</div>
<blockquote cite="mid:4C37B04C-6B11-47E7-A34D-E5D753960F58@qmx.me"
type="cite">
<pre wrap="">What about returning a PagedList<T> (and using guava's ForwardingWhatever to decorate the list with the paging info)?
</pre>
</blockquote>
So something like PagedListExample?<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="https://gist.github.com/d835d4a56d4d25e4ca9a">https://gist.github.com/d835d4a56d4d25e4ca9a</a><br>
<blockquote cite="mid:4C37B04C-6B11-47E7-A34D-E5D753960F58@qmx.me"
type="cite">
<pre wrap="">
On 11/01/2013, at 14:14, Summers Pittman <a class="moz-txt-link-rfc2396E" href="mailto:supittma@redhat.com"><supittma@redhat.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
On 01/11/2013 07:46 AM, Matthias Wessendorf wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Of course, sending simple request parameters to the server is easy, in
every library
(using Dan's CURL client example)
```
URL=
<a class="moz-txt-link-rfc2396E" href="http://controllerdemo-danbev.rhcloud.com/aerogear-controller-demo">"http://controllerdemo-danbev.rhcloud.com/aerogear-controller-demo"</a>
curl -i --header "Accept: application/json" "$URL/cars?page=0&perPage=4"
```
In terms of an client API, that wants to scroll through the cars (like
in this demo), I was wondering if some "PagingContext" (or
"ResultSet") API is needed...
// issues a request with ?page=0&perPage=4
PagingContext pc = client.request(someCars...);
// issues a request with ?page=0&perPage=4
pc.next()
// issues a request with ?page=1&perPage=4
pc.next()
// issues a request with ?page=0&perPage=4
pc.back()
NOT sure, but IMO a little higher level abstraction would be nice,
instead of having the end users of the "paging API" applying the
values for 'page' and 'perPage' manually.
Any thoughts? (Not sure if this has been brought up before)
-M
</pre>
</blockquote>
<pre wrap="">+1 for a higher level abstraction
As far as how it will mesh with Pipe and such I am thinking
<a class="moz-txt-link-freetext" href="https://gist.github.com/4511860">https://gist.github.com/4511860</a>
</pre>
<blockquote type="cite">
<pre wrap="">
On Fri, Jan 11, 2013 at 12:39 PM, Matthias Wessendorf
<a class="moz-txt-link-rfc2396E" href="mailto:matzew@apache.org"><matzew@apache.org></a>
wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
was there already some discussion (and proposal) for paging APIs on the client ?
It would be nice if the public client API semantics are somewhat
identical on the different platforms.
(I guess it's a MUST :))
Any pointers to gists etc are welcome
Thx
--
Matthias Wessendorf
blog:
<a class="moz-txt-link-freetext" href="http://matthiaswessendorf.wordpress.com/">http://matthiaswessendorf.wordpress.com/</a>
sessions:
<a class="moz-txt-link-freetext" href="http://www.slideshare.net/mwessendorf">http://www.slideshare.net/mwessendorf</a>
twitter:
<a class="moz-txt-link-freetext" href="http://twitter.com/mwessendorf">http://twitter.com/mwessendorf</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
aerogear-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a>
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
aerogear-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>