Re: Redirection and creation <was> Re: Container Independence

From: Dhanji R. Prasanna <>
Date: Sat, 14 Apr 2007 00:33:54 +1000

On 4/14/07, Marc Hadley <> wrote:
> I agree that most things in there could be injected as method
> parameters but to do so separately would require 10 new annotations
> (assuming all the request data obtainable remains desirable). Perhaps
> we should consider a somewhat coarser granularity, e.g. we could have
> an injectable UriInfo interface that contains the HttpRequestContext
> methods associated with the request URI rather than injecting each
> part of the information separately.

Im open to this, but I dont see a problem with several annotations. You
choose the ones you need and ignore the rest; whereas with all-purpose
interfaces you are forced to understand the semantics of the entire object
(and its roles) or risk uninformed use.

> Or why Representation<T> doesnt encapsulate metadata returned in
> > the response. Is this the 20/80 facilitator? If so I'd worry about
> > later.
> >
> I don't understand that comment, Representation<T> does encapsulate
> metadata returned in the response: content type, content language,
> content location, last modified and etag.

Sorry, that was a bit of a run-on. I meant that I believe Representation<T>
fulfills the metadata requirement and that I do not see the need for
additional artifacts (such as HttpResponse and HttpResponseContext) to serve
the same purpose.