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.

Date of Patent:
Aug. 23, 2016

Filed:

Dec. 26, 2006
Applicants:

William M. Quinn, Lexington, KY (US);

Ron E. Pontrich, Lexington, KY (US);

Ramya Sethuraman, Lexington, KY (US);

Christopher D. Price, Georgetown, KY (US);

Christopher A. Hyland, Foxboro, MA (US);

Aseel Aziz-gomez, Lexington, KY (US);

Inventors:

William M. Quinn, Lexington, KY (US);

Ron E. Pontrich, Lexington, KY (US);

Ramya Sethuraman, Lexington, KY (US);

Christopher D. Price, Georgetown, KY (US);

Christopher A. Hyland, Foxboro, MA (US);

Aseel Aziz-Gomez, Lexington, KY (US);

Attorney:
Primary Examiner:
Assistant Examiner:
Int. Cl.
CPC ...
G06F 15/16 (2006.01); H04L 12/18 (2006.01); H04L 29/08 (2006.01);
U.S. Cl.
CPC ...
H04L 12/1827 (2013.01); H04L 67/02 (2013.01);
Abstract

A system for providing resource-based synchronization between clients in a Web-based real-time collaboration, in which a session front end on the server layers a transaction history on top of all session resources. HTTP operations are issued by client systems to request changes to session resources and to request session updates. The HTTP resource change requests include hierarchical pointers containing session identifiers and resource identifiers within a URL. The client generated resource change request operations may be HTTP PUT, HTTP DELETE, and HTTP POST commands. The HTTP session update request operations may be HTTP GET commands. A session front end stores each received resource change request operation in a resource-specific transaction history of change request operations received from all client systems. The session front end maintains a current session state indicating the number of resource change request operations stored for each session resource. A last session state for each client system indicates the number of change request operations that client system has previously received for each session resource. For a session update, the session front end compares the last client session state for the requesting client with the current session state and determines the change request operations that need to be forwarded to the requesting client system to bring it up to date. The session front end removes negating change request operations from the change request operations forwarded to the requesting client system.


Find Patent Forward Citations

Loading…