Out of curiosity is there a reason why Resource isn't implemented as a subclass of Restlet? It seams like there is a lot of overhead in initializing a new Resource on every request especially when a lot of salient features such as what methods,variants, etc that are supported tend to static for a give route to that resource.
Thanks, Dave On Mon, Mar 23, 2009 at 11:46 AM, Rob Heittman <rob.heitt...@solertium.com> wrote: > I'd be careful of judgement-words like "bad practices" since this implies > some universal level of harm in all cases. I think the current Finder > design is simplistic, flexible, and easy to implement. I think there is > also room for a more structured base implementation that exposes some > advantages for more complex resource object hierarchies. I don't think > these are mutually exclusive. > > On Mon, Mar 23, 2009 at 2:34 PM, Tal Liron <tal.li...@threecrickets.com> > wrote: >> >> Good point, Rhett. >> >> Well, let me put it this way -- do you think the current Finder design >> encourages bad practices for Restlet users? >> >> -Tal > > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1392294
