I would agree with those mappings.  My understanding from previous threads:

Restlet (and subclasses): part of the web application plumbing, long-lived,
must be thread safe.

Resource: ephemeral, created and destroyed on demand, need not be thread
safe.  Maps to one instance of a class of addressable items in the REST
paradigm.

I also tend to use Restlet (etc) to implement imperative styles (URIs
accessed to produce certain side effects), and Resource to implement more
functional styles, without side effects.

- R


On 2/8/08, Paul J. Lucas <[EMAIL PROTECTED]> wrote:
>
> Is there a guideline when one should extend Restlet vs. extens
> Resource?  My rationalization is that: if X represents some kind of
> "physical" resource, the one should extend Resource; if X represents
> some kind of service, e.g., a "search service," then one should
> extend Restlet.
>

Reply via email to