Sorry, I forgot to cc: the list...
--- Begin Message ---
En mi�, 2001-11-14 a 22:58, Davanum Srinivas escribi�:
> Raphael,
>
> The response time is ok....Not a problem. Yes, I had the same thoughts regarding a
>Portlet
> Container based on Cocoon2 that can leverage Cocoon2's new SAX based Aggregation
>capabilities. Do
> you have some code? Any pointers to previous discussion? etc... FYI, i have not
>looked at jetspeed
> code at all. Can you help by pointing me to the right direction? I might have a few
>cycles to
> spare.
Random thoughts:
A cocoon2 generator that takes as parameter a PSML document (+
registries) and aggregates the result as a page could be implemented. A
PSML document is a specification on how content (portlets) is to be
aggregated. (This could result in proposals for better PSML schema, ...)
A specification for portlet content Schema. Currently the portlets are
free to "spit" whatever content. A specification for document fragments
to be aggregate could be helpful to have interoperable XML portlets. I
have been thinking about this: have portlets restricted to flow and
block markup, and have the aggregator take care of the page layout, much
in that same way that they do in "paper newspapers".
A specification for declarative portlet actions. The idea is that the
portlet writer does not "code" urls, but specifies actions with
callbacks. This will be useful if we want to abstract the portlet writer
from media.
This are truly random thoughts :) Wish I had more time...
WRT to your code pointers, just look at the PSML example
(http://cvs.apache.org/viewcvs/jakarta-jetspeed/webapp/WEB-INF/psml/user/admin/html/default.psml?rev=1.8&content-type=text/vnd.viewcvs-markup
and also to the registries, to see our approach.
--- End Message ---
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
