Hi Justin, Yes, Restlet subclasses must be thread-safe. Note that the Resource class provides additional services compared to a Restlet subclass, like content negotiation.
Best regards, Jerome > -----Message d'origine----- > De : Stanczak Group [mailto:[EMAIL PROTECTED] > Envoyé : lundi 10 septembre 2007 19:45 > À : [email protected] > Objet : Re: Are Resources Cached? > > So a Restlet would need to be thread safe? I think what I'll do is > extend a Restlet with a custom class that supplies a URI to > the Router. > Because I'm having Pico handle IoC I'll have it supply an > array of these > custom classes to the application. I'll post the code asking > others to > look it over. Thanks. > > Rob Heittman wrote: > > > >> What I don't under stand is in the documents talk about > >> creating domain object using Resources, but doesn't have > the Finder > >> create them for you limit a developers control? > >> > > > > Yes. In trade for looser binding between a resource and the > > infrastructure that manages its URI space. > > > > I find it helpful to think of the Restlet Resource as a resource > > wrapper. It is not the actual application domain object itself, but > > rather a lightweight object which adapts a domain object to the HTTP > > and REST paradigm for the purpose of a single access operation. > > > > This requires trunk ... but we have found a really useful tactic to > > be putting things like caches and connection pools at the > Application > > level, and then in the Resource, do something like: > > > > ((MyApplication) getContext().getApplication()).getConnection(); > > > > Augment this with some error checking, to ensure that your Resource > > is being called in the Context you think it is, and this works > > quite well and makes for a very readable code base with minimal > > surgery to Finders, minimal storage at the Resource level, and > > less overstuffing of the Context. > > > > It is less loosely bound, and makes your Resource dependent on a > > particular Application, but if you know that constraint is true > > anyway ... it's pretty useful. > > > > > >> Wouldn't it be better to allow a developer to manage the creation > >> of their own objects? > >> > > > > Well, sure, as you said, with a custom Finder or by skipping the > > Finder/Resource paradigm altogether and just attaching a Restlet, > > you can do this. I don't think I've read anything where this is > > considered a Bad Thing. There have been a number of custom Finder > > cases posted to the list, I don't think I have anything new to add. > > > > But the Finder/Resource design is a pretty neat one for separation > > of concerns, and we have gotten a lot of value out of it. > > > > - R > > > > -- > Justin Stanczak > Stanczak Group > 812-735-3600 > > "All that is necessary for the triumph of evil is that good > men do nothing." > Edmund Burke
