IP Library › Granted Patent US 7,143,174
Granted Patent B2
US 7,143,174 · App. 10/064,118 · Granted Nov 28, 2006

Method and system for delayed cookie transmission in a client-server architecture

Assignee: The JPMorgan Chase Bank, N.A.
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,143,174
App. No.
10/064,118
Granted
Nov 28, 2006
Kind
B2
Abstract

In a client-server architecture, a semi-persistent connection between the client and the server allows delayed or asynchronous transmission of a cookie or token. Delayed or asynchronous transmission of the cookie allows initial web page generation and display while awaiting a slow cookie, such as a cryptographically generated cookie that might be used for single-session sign-on.

Claims (42)

1. A method for providing information to a client browser, the method comprising:

receiving a first request from a client at a server;

responsive to the first request, initiating a request by the server to create a token, wherein the token comprises a request by the client for a resource;

determining in response to the first request whether the token has been retrieved within a predetermined amount of time after receiving the first request; and

sending the token from the server to the client if the token has been retrieved within a predetermined amount of time after receiving the first request;

wherein, if the token was not retrieved within the predetermined amount of time after receiving the first request, the method further comprises sending from the server to the client display data and a first link corresponding to a program that listens for notification that the token has been retrieved, thereafter receiving a second request from the client at the first link, determining in response to the second request whether the token has been retrieved within a predetermined amount of time after receiving the second request, and sending the token from the server to the client if the token has been retrieved within the predetermined amount of time after receiving the second request.

2. The method according to claim 1 , further comprising:

wherein, if the token was not retrieved within the predetermined amount of time after receiving the second request, sending from the server to the client display data and a second link corresponding to a program that listens for notification that the token has been retrieved, thereafter receiving a third request from the client at the second link, determining in response to the third request whether the token is has been retrieved within a predetermined amount of time after receiving the third request, and sending the token from the server to the client if the token has been retrieved within the predetermined amount of time after receiving the third request.

3. A computer readable medium having computer executable code stored thereon, the code for providing information to a client browser, the code comprising:

code to receive a first request from a client at a server;

responsive to the first request, code to initiate a request by the server to create a token, wherein the token comprises a request by the client for a resource;

code to determine in response to the first request whether the token has been retrieved within a predetermined amount of time after receiving the first request;

code to send the token from the server to the client, the token has been retrieved within the predetermined amount of time after receiving the first request;

code to determine in response to the first request if the token was not retrieved within the predetermined amount of time after receiving the first request;

code to send from the server to the client display data and a first link corresponding to a program that listens for notification that the token has been retrieved in response to a determination that the token was not retrieved within the predetermined amount of time after receiving the first request;

code to receive a second request from the client at the first link;

code to determine in response to the second request whether the token has been retrieved within a predetermined amount of time after receiving the second request; and

code to send the token from the server to the client if the token has been retrieved within the predetermined amount of time after receiving the second request.

4. A programmed computer for providing information to a client browser, comprising:

a memory having at least one region for storing computer executable program code; and

a processor for executing the program code stored in the memory, wherein the program code comprises:

code for providing information to a client browser, the code comprising:

code to receive a first request from a client at a server;

responsive to the first request, code to initiate a request by the server to create a token, wherein the token comprises a request by the client for a resource;

code to determine in response to the first request whether the token has been retrieved within a predetermined amount of time after receiving the first request;

code to send the token from the server to the client if the token has been retrieved within the predetermined amount of time after receiving the first request;

code to determine in response to the first request if the token was not retrieved within the predetermined amount of time after receiving the first request;

code to send from the server to the client display data and a first link corresponding to a program that listens for notification that the token has been retrieved in response to a determination that the token was not retrieved within the predetermined amount of time after receiving the first request;

code to receive a second request from the client at the first link;

code to determine in response to the second request whether the token has been retrieved within a predetermined amount of time after receiving the second request; and

code to send the token from the server to the client if the token has been retrieved within the predetermined amount of time after receiving the second request.

5. The meted according to claim 1 , wherein die token comprises a cookie.

6. The method according to claim 1 , wherein the first link comprises a link to a clear gif.

7. The method according to claim 1 , wherein the server creates the token.

8. The method according to claim 1 , wherein a second server creates the token.

9. The method according to claim 1 , wherein the first link comprises a link to the server.

10. The method according to claim 1 wherein the first link comprises a link to a second server.

11. The method according to claim 1 , wherein the request comprises an http request.

12. The method according to claim 1 , wherein the token comprises a slow cookie.

13. The method according to claim 1 , wherein sending from the server to the client display data and a first link comprises sending html.

14. The method according to claim 2 , wherein the second link comprises a link to the server.

15. The method according to claim 2 , wherein the second link comprises a link to a second sewer.

Assignments (2)
CHANGE OF NAME Recorded Jul 26, 2013
From: JPMORGAN CHASE BANK
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 030890/0012 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 12, 2002
From: MILLER, LAWRENCE; DEANS, WILLIAM; MOORE, MIKE
To: JPMORGAN CHASE BANK
Reel/Frame 012791/0260 →
Continuity (1)
Related Publication 20030233459A1 · Dec 18, 2003