The lifecycle of the application lifecycle in the entire application is: Application startup to stop.
Session sessions You can set his time by default is 30 minutes when you close the browser and end this session the user starts the operation and produces a unique one
Request is to obtain information--through the user submitted form, query string, cookie, etc. to get information
The session is used by the server to hold some data (usually marked State, and of course it can save other)
Session is a server-side record variable that can track and record visitors ' actions, such as logging in, exiting, and so on.
Request used in data submission, form data, etc.
Cookie word it has an expiration date you can also set the time like one months a year
It says that the application lifecycle Shiite the entire application, which is too abstract for me as a beginner, and I've tried all sorts of situations myself.
Application: After submitting the form, display the form information, whether it is refreshing the page, turn off the browser to reopen the page or a browser to open, just submitted the form is valid, display the information page will display the information submitted before;
Session: Refresh the page, the information is still valid, but after you turn off the browser, enter the address to open is not valid
Request: This did not test, the book said that the use of server jump <jsp:forward> jump is valid, I think it should be said that the object attribute value can be passed, but through hyperlinks or the address bar of the jump information will be invalidated