On 4/23/06, 王曾wang_zeng <[EMAIL PROTECTED]> wrote: > > Graig,thank you for your answer. > Acorrding to your answer, JSF component tree should be created everytime a > request arrives. Will it be a waste of time. > Asp.net use hidden-type input html tag to record the status of the > component > tree. Dose JSF do it the same way? > > JSF gives you a choice of client-side or server-side state saving. If you select client side, it is done in a manner very similar to how ASP.NET works (with a hidden field). If you select server side, the state is stored in session scope.
>From a strictly *computational* performance point of view, server side state saving will generally be better, because the state does not actually have to be serialized and deserialized. But, of course, you are trading off memory between requests for the computational overhead of reconstructing the tree. There is no one right answer for all applications, so it is nice to have a choice so you can try both and select the one that works better overall for your particular scenario. Craig
