[EMAIL PROTECTED] wrote:
[EMAIL PROTECTED]">



Santiago Gala wrote:

We are already supporting, in not yet public code, HTML and WML with the
same PSML file using a final media adapted XSLT transformation. All
portlets generate XML, and the aggregation process is a matter of
following the PortletSet structure and generating SAX events on the fly.
This events are processed by a final Stylesheet, that formats the
output. I think that the code is even simpler than the current code.

Santiago,

how many personalized portal pages per second can you serve using this
approach and what is the memory usage and the number of objects created per
request ?

Best regards,
We are not able to test until when we get it working with just released Xalan2 (much more adapted to SAX XSLT transformations). But I will tell you soon. In any case, I would not expect it to be slower than current Jetspeed. And experience tells me that if it is not ready for high traffic portals now (which remains to be seen), it will be in one or two generations of hardware (read six months / one year).

I think the revolution now is on getting people aware that style should be separated from content as far as possible, as they are serving only HTML now, but they will be serving WML, VoiceML, XHTML (in several variants) real soon.






--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Search: 
List Help?:          [EMAIL PROTECTED]



Reply via email to