Raphael Luta wrote:
> > I would think that a device negotiation layer as you could
> call Cocoon would
> > be extremely helpful working towards different devices - it
> does already
> > quite a lot of things in terms of user agent detection and the like.
> >
>
> The browser detection of Cocoon definitely needs an
> improvement. The main
> issue being that it detects browsers and not *capabilities*.
Some people on the Cocoon mailing list have start sending in patches doing
some 'browscap' style UA detection. So I suppose this is heading into the
right direction.
> Such a piece of code would be of tremendous use for many
> Apache projects :
> Turbine, Cocoon, Jetspeed, Jyve... and so should probably be
> considered
> part of the Avalon project.
>
> Of course, the difficult task in this is to keep track of all the
> browsers capabilities...
Problem is also that the interpretation of a certain capability sometimes
differs from browser to browser. It's nice to know that both XYZ and ABC
support JavaScript 3.98, but in our reality we would end up designing
towards specific browsers, since they have a different interpretation for a
certain JavaScript statement.
I know this is kind of pragmatic, but reality kicks in when you design &
build websites for a living.
> For me: dynamic = user customizable. I'm waiting for Stefano proposal
> to see what hooks would be available for jetspeed within the
> sitemap, but
> I fear SoC (separation of concerns, Stefano's mantra for
> Cocoon 2) issues.
The Action component gives you the possibility to specify some code (which
has a required minimal interface) to invoke during a certain pipeline.
Giacomo Pati told me you had full access to the Cocoon internals during the
execution of that class but you could do all kinds of back-end stuff also
within it (like accessing a DB, checking the session, etc...)
That's what I understood from it, but IANAProgrammer :-|
SoC is an issue of course, but offering a web publishing platform without
some sound integration with a web application platform doesn't make much
sense to me also, and I can't assume Stefano hasn't been thinking about that
one also.
After all, the sitemap could also be considered as being some kind of basic
webapp (mapping the URI namespace into serverside content generation &
filtering processes, where personalization sure needs to be an issue).
</Steven>
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
