On Thu, 2012-08-30 at 19:26 +0200, Mick Semb Wever wrote: > > Request regroups several concerns into a single interface, the most > > significant are: > > - attributes regrouped by "context". We usually assume these "contexts" > > are hierachical and related to the lifespan of the objects they contain, > > after the fashion of the Servlet API, but very little is explicitely > > defined by the Request API. > > - a Writer serving as output for the renderer. > > "resource loading" is another concern Request is currently responsible > for.
brainfart. ApplicationContext is, although the request may be one way of getting to it. ~mck -- "misunderstanding is never ended by by an argument but by tact, diplomacy, conciliation and a sympathetic desire to see the other person's viewpoint" Buddha | http://github.com/finn-no | http://tech.finn.no |
signature.asc
Description: This is a digitally signed message part
