Web hosting india - 350 Part III . Document Objects Reference A
350 Part III . Document Objects Reference A cookie record Among the fields of each cookie record are the following (not necessarily in this order): . Domain of the server that created the cookie . Information on whether you need a secure HTTP connection to access the cookie . Pathname of URL(s) capable of accessing the cookie . Expiration date of the cookie . Name of the cookie entry . String data associated with the cookie entry Notice that cookies are domain-specific. In other words, if one domain creates a cookie, another domain cannot access it through the browser s cookie mechanism behind your back. That reason is why it s generally safe to store what I call throw away passwords (the username/password pairs required to access some free registration-required sites) in cookies. Moreover, sites that store passwords in a cookie usually do so as encrypted strings, making it more difficult for someone to hijack the cookie file from your unattended PC and figure out what your personal password scheme may be. Cookies also have expiration dates. Because some browsers may allow no more than a fixed number of cookies (300 in NN), the cookie file can get pretty full over the years. Therefore, if a cookie needs to persist past the current browser session, it should have an expiration date established by the cookie writer. Browsers auto matically clean out any expired cookies. Not all cookies have to last beyond the current session, however. In fact, a sce nario in which you use cookies temporarily while working your way through a Web site is quite typical. Many shopping sites employ one or more temporary cookie records to behave as the shopping cart for recording items you intend to purchase. These items are copied to the order form at checkout time. But after you submit the order form to the server, that client-side data has no particular value. As it turns out, if your script does not specify an expiration date, the browser keeps the cookie fresh in memory without writing it to the cookie file. When you quit the browser, that cookie data disappears as expected. JavaScript access Scripted access of cookies from JavaScript is limited to setting the cookie (with a number of optional parameters) and getting the cookie data (but with none of the parameters). The original object model defines cookies as properties of documents, but this description is somewhat misleading. If you use the default path to set a cookie (that is, the current directory of the document whose script sets the cookie in the first place), then all documents in that same server directory have read and write access to the cookie. A benefit of this arrangement is that if you have a scripted application that contains multiple documents, all documents served from the same directory can share the cookie data. NN and IE, however, impose a limit of 20 document.cookie
Searching for affordable and proven webhost to host and run your servlet applications? Go to Linux Web Hosting services and you will find it.