Andrew, Tony
Thanks for your feedback.
I'm a little concerned about the overhead involved in getting the
information I want out of the
user agent string (browser, version and platform), the more so since
in the worst case it would
be done for every Cocoon request. I like the way LocaleAction
"remembers" what it has done
in the session and I want to try and do something like that.
So I am taking the plunge and writing a BrowserAction. When it's
working for me, I'll make it
available as alpha-code if anyone else is interested.
Steve
On 17 Feb 2006, at 01:01, Stephen Winnall wrote:
I am looking for a way to get information about the user's browser
in a transformation in a
Cocoon pipeline. I may be looking for the wrong thing, or trying to
go about it in the wrong
way, so I'd be grateful for any advice.
I want to handle browser differences in an XSLT file rather than in
the sitemap. I realise that
I could use BrowserSelector if I wanted the logic to be in the
sitemap, but I think I have a
cleaner solution if I can put the logic into a transformation. An
action along the lines of
LocaleAction would seem to me to fit the bill.
I've spent some time googling for BrowserAction and variations of
that, but I haven't found
anything and suspect that I may have to write the thing myself.
Does such a thing already
exist? Or is there already an elegant way of passing the name of
the browser (ideally with
version and OS) to an XSLT in a pipeline?
Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
