cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timm, Sean" <>
Subject RE: Better and Better and RT
Date Fri, 10 Nov 2000 13:00:43 GMT
Ross Burton [] wrote:
> On Thu, 9 Nov 2000, Timm, Sean wrote:
> > It would be cool if the BrowserCapabilitySelector 
> interacted with something
> > that emulated CC/PP.  That way, when CC/PP was finally 
> supported on clients,
> > we could jump over to it right away for those that 
> supported it while still
> > emulating it for those that didn't.
> > 
> > Just brainstorming here, so don't flame me too much...:)
> Had a good think about this in the shower this morning...  
> how about this
> for a next generation capability selector (it may be totally 
> wrong as I've
> just got up)

Don't worry...I haven't gone to bed, yet, so I doubt I'll even notice.  :)

> When a pipeline needs to know about the browser's 
> capabilities, it calls
> 	<act type="extract-browser-ccpp"/>
> Which parses any CC/PP headers in the request object, then 
> looks up the
> user-agent in a database and merges in the CC/PP data found 
> there. This
> way we can support current browsers by writing all of the metadata in
> CC/PP notation, but it is extendable to future browsers too.  Also the
> Accepts header is parsed and added to the model. The object 
> containing the
> browser profile is added to the object model for the current 
> request, so
> it is accessible by the rest of the pipeline.

That was what I was trying to say...:)

> (Question: how does the WAP capability stuff compare to 
> CC/PP?  Is it is a
> subset of CC/PP?)

View raw message