<br><br><div class="gmail_quote">On Wed, Jan 16, 2013 at 2:58 PM, Bruno Oliveira <span dir="ltr"><<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If the data doesn't exist HTTP 204 is a good fit. Just don't understand why we need to interrupt the app workflow, because the data doesn't exist.<br></blockquote><div><br></div><div><br></div><div>
<p class="p1">Interesting idea, but I am not sure… if we want to "expose" the 204… since the idea of a pipe was/is to encapsulate some of the underlying bits.</p><p class="p1"><br></p><p class="p1"><br></p></div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<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>
<br>
<br>
On Wednesday, January 16, 2013 at 11:52 AM, Matthias Wessendorf wrote:<br>
<div><div class="h5"><br>
><br>
> On Wed, Jan 16, 2013 at 2:48 PM, Kris Borchers <<a href="mailto:kris@redhat.com">kris@redhat.com</a> (mailto:<a href="mailto:kris@redhat.com">kris@redhat.com</a>)> wrote:<br>
> > I would say returning the current page would be confusing. I would be fine with an exception or returning null as both can be handled pretty easily by a dev. I would say an exception may be more useful since it will tell the dev exactly what was wrong instead of their app choking in a null return but I am open to both.<br>
> ><br>
> > ><br>
> > > For offset > totalNbPages :<br>
> > > - throwing an exception ?<br>
> > > - returning null ?<br>
> > > - returning last page ?<br>
> ><br>
> ><br>
> ><br>
> > I would say same as above. Returning last page may be confusing but others are acceptable with a preference toward an exception.<br>
><br>
><br>
> +1 on an exception<br>
><br>
> -M<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>
</div></div>> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a> (mailto:<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>)<br>
<div class="HOEnZb"><div class="h5">> <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>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <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>