cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ovidiu Predescu <ovi...@cup.hp.com>
Subject [PATCH] browser database capabilities
Date Sun, 29 Oct 2000 22:59:18 GMT
The following patch extends the browser support in Cocoon 1.x, adding the
ability to detect the browser type using the Accept: header, in addition to the
User-agent: header. This way WAP browsers not described by their user-agent
still work correctly as long as they send the text/vnd.wap.wml MIME type in the
Accept: header.

In addition to this, browser descriptions have been moved out of
cocoon.properties into an XML file, which is intended to hierarchically
describe browsers and their capabilities. Currently the browser description is
very WAP-oriented, however new browsers can be described easily. A particular
browser description is passed as an argument to the XSLT processor so that
decisions based on it can be taken at the time of page generation.

The XML browser capabilities file is translated at compile time into a Java
class. The class can be dynamically reloaded at runtime when the XML file
changes; I don't plan support for this feature in C1, in C2 things seem to be a
easier.

The browser capabilities database is an important piece of the WML support, as
determining what features are available on a device is currently impossible.
The CC/PP standard will take some time to be implemented by various vendors and
until then this seems to be the only reasonable way to implement it. I plan to
extend the current support with a way to determine changing of dynamic features
in the browser (like Java(Script) enabled/disabled, accept/disallow fax receive
on cell phones etc.).

I believe this is a good feature to have, is anybody interested in having it?

Regards,
Ovidiu

-- 
Ovidiu Predescu <ovidiu@cup.hp.com>
http://orion.nsr.hp.com/ (inside HP's firewall only)
http://www.geocities.com/SiliconValley/Monitor/7464/


Mime
View raw message