The Httpsession Interface
TIle HttpSession interface is implemented hy the server. It enables a servlet to read and write the stall’! information that is associated with an HTTP session All of these methods throw  Explain if the session has already been invalidated.

The Http Session Blending letchner  Interface

The Http Session Binding Listener interface is implemented by objects that need tobe notified when they are bound to or unbound from an H1TP session. The methods.rha! are invoked when an object is bound or unbound.are.the following: void the event object that describes.

The HttpSesslonContext Interface
The HttpSession<;ontext interface is implemented by the server. It enables a settler to access sessions that are associated with it. A method is declared to return an enumeration of all the session IDs in the context. Its signature is the following: Enumeration gadgets{ ) Another method, which has the following signature, can map a session ID to an Http Session object Http Session get Session(String id) Here, id in the session 10

The Cookie Class

The Cookie class encapsulates a cookie. A rookie is stored on a client and contains state information. Cookies are valuable for tracking user activities. For example, assume that a user visits nil online bookstore. A cookie can save the user’s name, address, and other information. The user does not need to enter this data each time he or she visits the bookstore.

. A servlet can write a cookie to a user’s machine via the add Cookie( ) method of the HttpServletResponse interface, The data for that cookie is then included in the header of the HTTP response that is sent to the browser. The names and values of cookies arc stored on the user’s machine. Some of the information that is saved includes the cookie’s: name
II value
a expiration domain and path The expiration date determines when this cookie is deleted from the user’s machine. If an expiration date is not explicitly assigned to a cookie, it is deleted when the current browser session ends. Otherwise, thl! cookie is saved in a file on the user’s machine.The domain and path of the cookie determine when it is included in the header of an HTTP request. If the user enters a URL whose domain and path match these values, the cookie is then supplied to the Web server. Otherwise, it is not.The only-constructor for Cookie has the following signature : Cookie(String name, String Noelle Here, the name and value of the cookie arc supplied as arguments to the constructor.

[vfb id=1]

Share This