cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <ross.bur...@blueyonder.co.uk>
Subject RE: Better and Better and RT
Date Fri, 10 Nov 2000 14:50:22 GMT
> > 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...:)

Excellent!

> > (Question: how does the WAP capability stuff compare to
> > CC/PP?  Is it is a
> > subset of CC/PP?)
>
> From what I can tell, it is incorporated within it.  The
WAP group
> originally came up with their own set up detailed
requirements and
> specifications, but it looks like those have been
incorporated into the
> CC/PP requirements.

Oh good - any idea where the details of the WAP use is?

> > Then a SelectorFactory can be created which knows of the
> > object added to
> > the object model, and can react upon it.  Calls such as
"supports
> > JavaScript 1.2", "supports frames", "accepts image/png"
etc are now
> > trivial examinations of the object.
>
> Yes, yes, yes!  :)

I know!  This is looking good...

> > Comments?  I'm going to try and print out the CC/PP specs
> > today so I can
> > have a read of them and work this one out.
> >
> Good luck!

Thankyou!  I've thought of a problem with this, but I've
printed out the CC/PP
docs so I'll read them on the way home and write a mail tonight.

Ross Burton

Mime
View raw message