web applications - In what scenario is stateful better than stateless for the web? -
I have always advocated the Stateless Web, but I would like to know what advocates of useful web are saying.
Do you have any situation where statewide state is more suitable than Stateless?
Our project uses the Wicket Web Framework, which allows state-wide or stateless interaction stateful pages
- Using a state page in the wicket makes it easy to update partial pages by using the AJAX frame of wickets
- Stateful is a more "intuitive" Programming model, for example, in a wicket page class, I have server side And can declare a private member field do, it can set the page loads, and hits every time some updates a Ajeaks request page.
- During the handling of the request, the user stops the most common millennium problems in web thier by syncing on the session object.
- Storing the status on the server side can improve occasionally performance; For example, an object that is ready to take time to build, but should be available on the page, when the page is first institated, then can only be loaded once.
can also be implemented as stateless - you just have to store the state on the customer, and submit all relevant state information to each request.
Link to wicket:
Comments
Post a Comment