Hey Scott - On Feb 19, 2008 2:11 PM, Scott O'Bryan <[EMAIL PROTECTED]> wrote: > Hey Andy, why does RequestContext need this method? Is this something > that's will change on a per-request basis?
The plan is for the accessibility "profile" to be a sibling to the existing RequestContext accessibility "mode" and to follow the same lifecycle - ie. parsed from trinidad-config into the RequestContextBean, then exposed via the RequestContext, and promoted up to the RenderingContext for ease of use. I believe that this is the same lifecycle that is used for all of the trinidad-config properties (eg. see the recently added animation-enabled property). I would feel uncomfortable implementing a specialized solution specific to accessibility-profile. If we need to implement a new strategy for how we surface our trinidad-config properties, I would prefer that we tackle that generically rather than in the context of the accessibility profile feature. Does that sounds reasonable? Andy
