<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jan 16, 2013, at 7:58 AM, Bruno Oliveira <<a href="mailto:bruno@abstractj.org">bruno@abstractj.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">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 style="margin: 0px; font-size: 12px; color: rgb(50, 51, 51); ">I would prefer that an exception is thrown client side before a request is ever sent to the server. That way we save the http request which is important on mobile.</div><div style="margin: 0px; font-size: 12px; color: rgb(50, 51, 51); "><br></div><div style="margin: 0px; font-size: 12px; color: rgb(50, 51, 51); ">That being said, then the issue becomes what if that page does exist but we don't allow the request because the data was updated since our last read? Then we wouldn't know without another read happening.</div><div style="margin: 0px; font-size: 12px; color: rgb(50, 51, 51); "><br></div><div style="margin: 0px; font-size: 12px; color: rgb(50, 51, 51); ">Hmmm, interested in other opinions since relying on a 204 or any status from the server couples the client to the server impl but if we don't allow the request, that could also cause issues.</div><blockquote type="cite"><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><br><blockquote type="cite"><br>On Wed, Jan 16, 2013 at 2:48 PM, Kris Borchers <<a href="mailto:kris@redhat.com">kris@redhat.com</a> (<a href="mailto:kris@redhat.com">mailto:kris@redhat.com</a>)> wrote:<br><blockquote type="cite">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><blockquote type="cite"><br>For offset > totalNbPages :<br>- throwing an exception ?<br>- returning null ?<br>- returning last page ?<br></blockquote><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></blockquote><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/">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf">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> (<a href="mailto:aerogear-dev@lists.jboss.org">mailto:aerogear-dev@lists.jboss.org</a>)<br><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote><br><br><br>_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/aerogear-dev<br></blockquote></div><br></body></html>