Patrick Casey wrote:
Tapestry though, is architected around the concept of whole page
rendering. One can't guarantee that a component will render properly outside
of the context of its page. Which means, even if I only want to refresh
1/100th of a page, I still need to render the whole thing on the server,
trim out the part I want to refresh, and push that back to the client. So I
cut down on my wire traffic, and I save the user a page load, *but* the
server is still building a full page.
This is an important limitation of Tapestry component model that should
be targeted, if true, don't you think? I mean, a component - by
definition - is a black box. A component that depends on its container
page being rendered for proper rendering breaches that encapsulation
(note that this is different of just a component who needs its container
page to *exist* for proper rendering - in this case we don't have to
render the whole page, just to have it in memory).
I was talking about this in the Tacos list. Components, should IMO, be
rendereable on their own, instead of needing the full page render cycle
to work. A server-side component model in memory would help in this
respect, I think.
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
