The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Jun. 12, 2012
Filed:
Dec. 19, 2006
William M. Quinn, Lexington, KY (US);
Erik J. Burckart, Raleigh, NC (US);
Brian G. Cline, Hebron, KY (US);
James P. Galvin, Jr., Georgetown, KY (US);
Christopher D. Price, Georgetown, KY (US);
Thomas Schaeck, Boeblingen, DE;
William M. Quinn, Lexington, KY (US);
Erik J. Burckart, Raleigh, NC (US);
Brian G. Cline, Hebron, KY (US);
James P. Galvin, Jr., Georgetown, KY (US);
Christopher D. Price, Georgetown, KY (US);
Thomas Schaeck, Boeblingen, DE;
International Business Machines Corporation, Armonk, NY (US);
Abstract
A highly scalable and highly responsive RTC system uses asynchronous or non-blocking I/O and HTTP response queuing to avoid server overload. The system distinguishes between two types of requests: an update request and a change request. An update request is a request used to fetch an update or change notification. A change request is a request to change some data related to the real-time session. For a given RTC session, the server first checks whether any updates exist for an update request. If an update exists, the server code can send an immediate response to the client. However, if no update exists, the server code application sets a well-defined HTTP response header, and then responds. Once the server code application responds, all application server resources are freed, and the application server is free to handle the next requests without blocking any thread.