Persistant Client State in a Hypertext Transfer Protocol Based Client-Server System
a client-server system and hypertext transfer technology, applied in the field of communication in a client-server computer system, can solve the problems of increasing the complexity of the interaction, the communication model under the conventional web environment provides a very limited level of interaction between clients and servers, and the inability to easily access the web by a technically untrained person,
- Summary
- Abstract
- Description
- Claims
- Application Information
AI Technical Summary
Benefits of technology
Problems solved by technology
Method used
Image
Examples
example 1
[0067] A client system requests a Web document from the Web server “telemarking.acme.com” and receives in response:
Set-Cookie: CUSTOMER=WILE.sub.--E.sub.--COYOTE; path= / ;
expires=Wednesday, Nov. 9, 1999 23:12:40
[0068] The client system stores this cookie in a local (client-side) storage unit (e.g. mass storage 127 or memory 125). Since no domain name was specifically identified, the domain will be set to “telemarking.acme.com” since that is the domain name of the server that generated the cookie. When the client later makes an http request for a document in any path (since the path is “ / ”) of a server system in the telemarking.acme.com domain, the client sends:
Cookie: CUSTOMER=WILE.sub.--E.sub.--COYOTE
[0069] Assuming the client system makes another request to the telemarking.acme.com domain, the client might receive another cookie from the server such as:
Set-Cookie: PART.sub.--NUMBER=ROCKET.sub.--LAUNCHER;
path= /
[0070] The client will locally store this additional cookie....
example 2
[0074] Assume that all of the transactions of Example 1 have been cleared. A client system then requests a Web document from the Web server “telemarking.acme.com” and receives in response:
Set Cookie: PART.sub.--NUMBER=ROCKET.sub.--LAUNCHER.sub.--1;
path= /
[0075] The client stores this cookie in a local (client-side) storage unit. Since no domain name was specifically identified, the domain will be set to “telemarking.acme.com”. When the client later makes a request to a document in any path of a system in the telemarking.acme.com domain, the client sends back the following data as information:
Cookie: PART.sub.--NUMBER=ROCKET.sub.--LAUNCHER.sub.--1
[0076] Assuming the client continues to access the “telemarking.acme.com” server, the client may later receive from the server:
Set-Cookie: PART.sub.--NUMBER=RIDING.sub.--ROCKET.sub.--23;
= / ammo
[0077] new cookie has the same name (PART.sub.--NUMBER) as an old cookie stored on the client system. Note that the old cookie is not overw...
PUM
Login to View More Abstract
Description
Claims
Application Information
Login to View More 


