What is the difference between javax.faces.STATE_SAVING_METHOD client and server?
In short, server-side-state stores information held by the UI components (ie the “widgets”) in the HTTP Session, while client-side state stores it in hidden fields in the page sent back to the user. Client-side-state scales much better for very large numbers of users, as no memory is required on the server for user state. However the disadvantage is that more data gets transferred across the network for each request. Any session-scoped managed beans still remain in the http session, even with client-side-state selected; this flag only affects where the JSF implementation stores data that the UI components hold internally. For the technical details, see: • http://java.sun.com/javaee/5/docs/tutorial/doc/bnavu.html#bnavz • http://java.sun.com/javaee/5/docs/tutorial/doc/bnaxj.
Related Questions
- If accessing the Project Server 2007 server via the Project Web Access Client, do they need additional software if accessing locally, ie. over the local LAN?
- How do I install the PowerEdge Expandable RAID Controllers Power Console remote client utility on a console server running Windows NT?
- How do I use my server clock for the current time instead of relying on clients browser?
