Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Message-ID: <85CDFD92C550D311A1A40008C7DFA81A37B346@firewall.altacast.com>
From: "Timm, Sean" <STimm@mailgo.com>
To: "'cocoon-dev@xml.apache.org'" <cocoon-dev@xml.apache.org>
Subject: RE: Better and Better and RT 
Date: Thu, 9 Nov 2000 13:44:34 -0700 
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"

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...:)

- Sean T.

> -----Original Message-----
> From: Ovidiu Predescu [mailto:ovidiu@cup.hp.com]
> Sent: Thursday, November 09, 2000 12:58 PM
> To: Donald Ball
> Cc: cocoon-dev@xml.apache.org
> Subject: Re: Better and Better and RT 
> 
> 
> On Thu, 9 Nov 2000 14:29:05 -0500 (EST), Donald Ball 
> <balld@webslingerZ.com> 
> wrote:
> 
> > On Sat, 4 Nov 2000, Ross Burton wrote:
> > 
> > > I have plans to write both of these.  I'm currently 
> finishing a spec for
> > > BrowserCapabilitySelector which will include Accepts as a 
> parameter, and
> > > IIRC a ParameterMatcher was posted recently which might 
> be able to be
> > > changed to a selector.
> > 
> > any luck searching for an open database of browsers and their
> > capabilities, or do we still need to write our own? :)
> 
> What kind of browser capabilities are you looking for?
> 
> As I said in an earlier posting, I have already implemented 
> something similar
> for C1. I posted the patch on the mailing list a while ago. 
> It should be fairly
> easy to port the code to C2, although I admit I didn't look 
> at C2 as much as I
> looked on C1.
> 
> The patch looks at the Accept: header if the user agent is 
> not known and
> generates the correct media type for Cocoon. When the user 
> agent is specified,
> Cocoon passes to the XSLT processor as an argument a DOM tree 
> with the browser
> capabilities. One can make use of this argument to generate a 
> customized
> mark-up page; I'm already doing it for WML browsers.
> 
> The initial code is aimed at supporting WML browsers, but it 
> can be extended
> easily to support HTML browsers as well. In fact the database 
> does contain a
> description of some HTML browsers, but nothing really serious.
> 
> Please let me know if you want me to repost the patch.
> 
> Regards,
> -- 
> Ovidiu Predescu <ovidiu@cup.hp.com>
> http://orion.nsr.hp.com/ (inside HP's firewall only)
> http://www.geocities.com/SiliconValley/Monitor/7464/
> 
>