Sounds like a very convenient method. Most containers are going to adhere to what the client asks for. We'd still need to the multi-args version for containers that wish to ignore the client or have an indeterminate response.
On Thu, May 13, 2010 at 9:13 PM, Chirag Shah <[email protected]> wrote: > While we're at it.. what do you think about adding > RestfulCollection(List<T> entry, CollectionOptions options), and > deducing startIndex (from options), totalResults (from entry), > itemsPerPage (from options)? > > Thanks, > Chirag > > On Thu, May 13, 2010 at 4:26 PM, Paul Lindner <[email protected]> > wrote: > > I'm starting some cleanup getting ready for 2.0. This involves removing > > some deprecated code. The only one that we might want to keep is legacy > > body signing and/or strict content checks. I'm going to remove it for > now. > > If anyone needs it for 2.x let me know and I'll revert. > > > > * SocialSpiException class is removed, use ProtocolException instead > > > > * GuiceBeanConverter.DuplicateFieldException class is removed > > > > * RestfulCollection > > > > The constructor RestfulCollection(List<T> entry, int startIndex, int > > totalResults) is removed. > > Use the constructor with an items-per-page parameter instead. > > >
