<div dir="ltr">><span style="font-family:arial,sans-serif;font-size:13px">hrm... not sure I like that. This could wait for a later release. I am </span><span style="font-family:arial,sans-serif;font-size:13px">(personally) fine </span><span style="font-family:arial,sans-serif;font-size:13px">in supporting just one location (and our clients should default to it).</span><div style>
<span style="font-family:arial,sans-serif;font-size:13px">I'm cool with that and like I said, this has not been included in the server side spec yet. If we decide to wait until a later release we should remove this from the client api spec.</span></div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 17 January 2013 08:56, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Thu, Jan 17, 2013 at 8:47 AM, Daniel Bevenius<br>
<<a href="mailto:daniel.bevenius@gmail.com">daniel.bevenius@gmail.com</a>> wrote:<br>
>>perhaps I don't get it - but... our backend uses the headers for the web<br>
>> linking, AG-Limit etc, right?<br>
> Yeah, you are correct our backend is using headers for web linking and<br>
> total. We discussed [1] in the past the option to have the same information<br>
> in the body of the response instead of as HTTP headers, for example an<br>
> Object in a JSON response. The location of this information could then be<br>
> specified by the client to tell the server where it should place the<br>
> metadata.<br>
<br>
<br>
</div>hrm... not sure I like that. This could wait for a later release. I am<br>
(personally) fine<br>
in supporting just one location (and our clients should default to it).<br>
<div class="im"><br>
>>I think, it's OK to NOT send that limit/offset overhead to someone<br>
>>that knows about it already. That's what you are saying, right ?<br>
> Yep, so we would just return the 'AG-Total' in this case.<br>
<br>
</div>great :)<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
> [1]<br>
> <a href="http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Paging-Demo-td1173.html" target="_blank">http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Paging-Demo-td1173.html</a><br>
><br>
><br>
> On 17 January 2013 08:36, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br>
>><br>
>> On Thu, Jan 17, 2013 at 8:05 AM, Daniel Bevenius<br>
>> <<a href="mailto:daniel.bevenius@gmail.com">daniel.bevenius@gmail.com</a>> wrote:<br>
>> > I've been reading the client API spec and noticed that I completely<br>
>> > forgot<br>
>> > the parameter 'metadataLocation' that an endpoint could optionally<br>
>> > accept,<br>
>> > which indicates if the information related to paging should be returned<br>
>> > as<br>
>> > part of the data, or as HTTP Headers.<br>
>> > I'll update the server side spec if no one objects.<br>
>><br>
>> perhaps I don't get it - but... our backend uses the headers for the<br>
>> web linking, AG-Limit etc, right?<br>
>><br>
>> So why should we include a "location" header? I understood it more as<br>
>> a "generic" client feature:<br>
>> - Tell the pipe where (haha :-)) to look (page/content VS header) for<br>
>> the "next", "previous" etc information<br>
>><br>
>><br>
>> > I also wanted to bring up that in the spec at the moment we have<br>
>> > specified<br>
>> > that we are only returning the 'total', and not the 'offset' and<br>
>> > 'limit'.<br>
>> > The reason for this being that the client sent the 'offset' and 'limit'<br>
>> > and<br>
>> > therefore already has this information. Does anyone have a different<br>
>> > take on<br>
>> > this?<br>
>><br>
>> I think, it's OK to NOT send that limit/offset overhead to someone<br>
>> that knows about it already. That's what you are saying, right ?<br>
>><br>
>> -M<br>
>><br>
>> ><br>
>> > thanks,<br>
>> ><br>
>> > /Dan<br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> > On 15 January 2013 19:44, Daniel Bevenius <<a href="mailto:daniel.bevenius@gmail.com">daniel.bevenius@gmail.com</a>><br>
>> > wrote:<br>
>> >><br>
>> >> +1 I'll start adding it tomorrow and keep it updated if no one objects.<br>
>> >><br>
>> >><br>
>> >> On 15 January 2013 19:42, Sebastien Blanc <<a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a>> wrote:<br>
>> >>><br>
>> >>> +1<br>
>> >>><br>
>> >>><br>
>> >>> On Tue, Jan 15, 2013 at 7:37 PM, Bruno Oliveira <<a href="mailto:bruno@abstractj.org">bruno@abstractj.org</a>><br>
>> >>> wrote:<br>
>> >>>><br>
>> >>>> +1 Any additions?<br>
>> >>>><br>
>> >>>> I just wondering about include it at<br>
>> >>>> <a href="http://aerogear.org/docs/specs/aerogear-rest-api/" target="_blank">http://aerogear.org/docs/specs/aerogear-rest-api/</a>. Makes sense?<br>
>> >>>><br>
>> >>>><br>
>> >>>> --<br>
>> >>>> "The measure of a man is what he does with power" - Plato<br>
>> >>>> -<br>
>> >>>> @abstractj<br>
>> >>>> -<br>
>> >>>> Volenti Nihil Difficile<br>
>> >>>><br>
>> >>>> On Tuesday, January 15, 2013 at 11:18 AM, Kris Borchers wrote:<br>
>> >>>><br>
>> >>>> This looks pretty good to me.<br>
>> >>>><br>
>> >>>> On Jan 15, 2013, at 3:26 AM, Daniel Bevenius<br>
>> >>>> <<a href="mailto:daniel.bevenius@gmail.com">daniel.bevenius@gmail.com</a>><br>
>> >>>> wrote:<br>
>> >>>><br>
>> >>>> Hi,<br>
>> >>>><br>
>> >>>> we've created the following gist[1] to specify our requirements for<br>
>> >>>> pagination. We can discuss this on the mailing list and then update<br>
>> >>>> the doc<br>
>> >>>> as we go along. This will later be turned into a page under the spec<br>
>> >>>> section<br>
>> >>>> of the site.<br>
>> >>>><br>
>> >>>> Nothing has been decide yet even if it might read like it has in the<br>
>> >>>> document.<br>
>> >>>><br>
>> >>>> [1] <a href="https://gist.github.com/4537431" target="_blank">https://gist.github.com/4537431</a><br>
>> >>>> _______________________________________________<br>
>> >>>> aerogear-dev mailing list<br>
>> >>>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
>> >>>> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
>> >>>><br>
>> >>>><br>
>> >>>> _______________________________________________<br>
>> >>>> aerogear-dev mailing list<br>
>> >>>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
>> >>>> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
>> >>>><br>
>> >>>><br>
>> >>>><br>
>> >>>> _______________________________________________<br>
>> >>>> aerogear-dev mailing list<br>
>> >>>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
>> >>>> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
>> >>>><br>
>> >>><br>
>> >>><br>
>> >>> _______________________________________________<br>
>> >>> aerogear-dev mailing list<br>
>> >>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
>> >>> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
>> >>><br>
>> >><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > aerogear-dev mailing list<br>
>> > <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
>> > <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
>> ><br>
>><br>
>><br>
>><br>
>> --<br>
>> Matthias Wessendorf<br>
>><br>
>> blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
>> sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
>> twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a><br>
>> _______________________________________________<br>
>> aerogear-dev mailing list<br>
>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
><br>
<br>
<br>
<br>
--<br>
Matthias Wessendorf<br>
<br>
blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a><br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</div></div></blockquote></div><br></div>