On 4/18/06, Jacob Hookom <[EMAIL PROTECTED]> wrote: > I think where the performance shows up is that with JSP, you are > buffering a lot of non-component data on each call, so the > 'instructions' for your tree have to be re-evaluated with each request.
Can you elaborate on what exactly is buffered in the JSP case. I have a rough idea of what you are talking about here but I don't know enough about the internals of JSP to completely understand this. I'm interested in some more specifics here. > When you get into AJAX or partial processing, this can get expensive! > > With Facelets, we have a static/shared set of instructions for building > component trees and inline content (what would be buffered with JSP) is > simply referenced by each user's component tree. So if you are using > AJAX to partially process only a few components, then you haven't > buffered/evaluated anything from your original document, just gotten > shared references, which less overhead on the server. Can you elaborate on shared references? Is the component tree still rebuilt in this scenario? I'm curious as to the specifics of the lifecycle in this use case. > -- Jacob Sean
