You are probably using client-side state saving. Thus, the encrypted string (and there's probably at least one copy of it for each form on your page) contains the entire jsf component tree state.
The data for this JSF session is essentially stored in your html page rather than in memory on the application server. On 12/23/05, Mike Duffy <[EMAIL PROTECTED]> wrote: > If you do a view source on the HTML for a page that was generated with JSF > you see lots of > encrypted values. The pages seem ridiculously huge. > > Has anyone else noticed this? :) > > I am sure there must be some good reason. I'm just curious to know what that > reason is. > > Thx. > > Mike > > > > __________________________________________ > Yahoo! DSL – Something to write home about. > Just $16.99/mo. or less. > dsl.yahoo.com > >
