Stephen, I guess there is a misunderstanding here: the "business layer"
concerns what's beyond and below JSF and the web - usually database
handling providing persistent data to component beans.
In case components have to deal with such layer - and AFAIK any complex
JSF application have to do it - then refreshing a single component
during a PPR cycle implies reading the contents of *all* other
components event if they will not be sent back to the client at all.
That's because all components are asked to be rendered anyway, and a
number of them are wired to the business layer to get actual contents.
Of course we can cache and speculate about the persistent layer not
being changed across PPR requersts - but the overall problem remains.
-- Renzo
Stephen Friedrich wrote:
Renzo Tomaselli wrote:
less DOM to update - but the business layer is fully involved as for
full-page requests.
For industrial applications this is usually the most significant cost.
What makes you think so?
On each full page load on my machine Firefox needs 200ms just to parse
and run the common Trinidad javascript (if Firebug is to be trusted).
Spending that time on the server side would allow for many, many full
JSF cycles.
Network latency, client side javascript execution, the usual browser
limit of max. 2 request to the same domain plus many other issues
limit the peformance much more.
Of course if by "industrial applications" you mean those with thousands
of _simultaneous_ accesses, then raw time spent on server side processing
probably really becomes more important.
