[aerogear-dev] Client Paging Strawman

[Bruno Oliveira]

HTTP 204 - Server response  

No data - client API  


--  
"The measure of a man is what he does with power" - Plato
-
@abstractj
-
Volenti Nihil Difficile



On Wednesday, January 16, 2013 at 12:16 PM, Matthias Wessendorf wrote:

>  
>  
> On Wed, Jan 16, 2013 at 2:58 PM, Bruno Oliveira <bruno at abstractj.org (mailto:bruno at abstractj.org)> wrote:
> > 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.
>  
>  
>  
> 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.
>  
>  
> >  
> >  
> > --
> > "The measure of a man is what he does with power" - Plato
> > -
> > @abstractj
> > -
> > Volenti Nihil Difficile
> >  
> >  
> >  
> > On Wednesday, January 16, 2013 at 11:52 AM, Matthias Wessendorf wrote:
> >  
> > >  
> > > On Wed, Jan 16, 2013 at 2:48 PM, Kris Borchers <kris at redhat.com (mailto:kris at redhat.com) (mailto:kris at redhat.com)> wrote:
> > > > 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.
> > > >  
> > > > >  
> > > > > For offset > totalNbPages :
> > > > > - throwing an exception ?
> > > > > - returning null ?
> > > > > - returning last page ?
> > > >  
> > > >  
> > > >  
> > > >  
> > > > I would say same as above. Returning last page may be confusing but others are acceptable with a preference toward an exception.
> > >  
> > >  
> > > +1 on an exception
> > >  
> > > -M
> > >  
> > >  
> > >  
> > > --
> > > Matthias Wessendorf
> > >  
> > > blog: http://matthiaswessendorf.wordpress.com/
> > > sessions: http://www.slideshare.net/mwessendorf
> > > twitter: http://twitter.com/mwessendorf
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org (mailto:aerogear-dev at lists.jboss.org) (mailto:aerogear-dev at lists.jboss.org)
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >  
> >  
> >  
> >  
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org (mailto:aerogear-dev at 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 at lists.jboss.org (mailto:aerogear-dev at lists.jboss.org)
> https://lists.jboss.org/mailman/listinfo/aerogear-dev