IP Library Granted Patent US 7,437,739
Granted Patent B1
US 7,437,739 · App. 10/636,951 · Granted Oct 14, 2008

Synchronizing data between a data store and a project management client tool

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,437,739
App. No.
10/636,951
Granted
Oct 14, 2008
Kind
B1
Abstract

An embodiment of the present invention is a technique to synchronize data between a data store and a project management client tool. An element in a project file is updated according to an event generated by a project tool in a client. A server is communicated by a request to request synchronization of the element. The server has a data store which contains an object corresponding to the element. The request is processed to synchronize the element with the object in the data store.

Claims (54)

1. A method comprising:

listening to a project tool to identify the firing of an event associated with an element, the element being one of a task and a resource stored in a project file on a client;

requesting synchronization of the element with an object in a data store on a server, the object corresponding to the element; and,

synchronizing the element with the object in the data store, the synchronizing comprising:

transforming the event into an action;

saving the action in an action list;

sending the action list to the server, sending the action list to the server comprising transforming the action list into a protocol request, the protocol request having a query string with a parameter list including an attribute of the action; and sending the protocol request to the server according to a protocol;

receiving a response from the server; and

parsing the response to determine status of the protocol request.

2. The method of claim 1 , the event being fired when the element is updated.

3. The method of claim 1 wherein the action comprises one of creation, deletion, and modification of the element.

4. The method of claim 1 , wherein sending the protocol request comprises:

sending the protocol request to a request processor running on the server such that the server can call a method to process the action.

5. The method of claim 4 wherein the request processor comprises a server-side page.

6. The method of claim 4 wherein the request processor comprises a server-side bean.

7. The method of claim 1 wherein sending the protocol request comprises sending the protocol request to the server according to a Hypertext Transfer Protocol (HTTP) protocol.

8. The method of claim 1 , the event being identified by an add-in module and the request being made by the add-in module.

9. An article of manufacture comprising:

a computer memory comprising data stored thereon, the data, when accessed by a machine, causing the machine to perform operations comprising:

listening to a project tool to identify the firing of an event associated with an element, the element being one of a task and a resource stored in a project file on a client;

requesting synchronization of the element with an object in a data store on a server, the object corresponding to the element; and,

synchronizing the element with the object in the data store, the synchronizing comprising:

transforming the event into an action;

saving the action in an action list;

sending the action list to the server, the sending comprising transforming the action list into a protocol request, the protocol request having a query string with a parameter list including an attribute of the action; and sending the protocol request to the server according to a protocol;

receiving a response from the server; and

parsing the response to determine status of the protocol request.

10. The article of manufacture of claim 9 , the event being fired when the element is updated.

11. The article of manufacture of claim 9 wherein the action comprises one of creation, deletion, and modification of the element.

12. The article of manufacture of claim 9 , wherein sending the protocol request comprises:

sending the protocol request to a request processor running on the server such that the server can call a method to process the action.

13. The article of manufacture of claim 12 the request processor comprises a server-side page.

14. The article of manufacture of claim 12 wherein the request processor comprises a server-side bean.

15. The article of manufacture of claim 9 wherein sending the protocol request comprises sending the protocol request to the server according to a Hypertext Transfer Protocol (HTTP) protocol.

16. The article of manufacture of claim 9 , the event being identified by an add-in module and the request being made by the add-in module.

17. A system comprising:

a processor; and

a memory coupled to the processor, the memory containing instructions that, when executed by the processor, causes the processor to:

listen to a project tool to identify the firing of an event associated with an element, the element being one of a task and a resource stored in a project file on a client;

request synchronization of the element with an object in a data store on a server, the object corresponding to the element; and,

synchronize the element with the object in the data store, the synchronizing comprising:

transforming the event into an action;

saving the action in an action list;

sending the action list to the server, the sending comprising transforming the action list into a protocol request, the protocol request having a query string with a parameter list including an attribute of the action; and sending the protocol request to the server according to a protocol;

receiving a response from the server; and

parsing the response to determine status of the protocol request.

18. The system of claim 17 , the event being fired when the element is updated.

19. The system of claim 18 wherein the action comprises one of creation, deletion, and modification of the element.

20. The system of claim 17 wherein the instructions causing the processor to send the protocol request comprises instructions that, when executed by the processor, causes the processor to:

send the protocol request to a request processor running on the server such that the server can call a method to process the action.

21. The system of claim 20 wherein the request processor comprises a server-side page.

22. The system of claim 20 wherein the request processor comprises a server-side bean.

23. The system of claim 17 wherein the instructions causing the processor to send the protocol request comprises instructions that, when executed by the processor, causes the processor to: send the protocol request to the server according to a Hypertext Transfer Protocol (HTTP) protocol.

24. The system of claim 17 , the event being identified by an add-in module and the request being made by the add-in module.

Assignments (12)
RELEASE OF SECURITY INTEREST Recorded Nov 9, 2017
From: WELLS FARGO BANK, NATIONAL ASSOCIATION (SUCCESSOR TO GENERAL ELECTRIC CAPITAL CORPORATION)
To: UNISYS CORPORATION
Reel/Frame 044416/0358 →
CHANGE OF NAME Recorded Oct 2, 2017
From: GOOGLE INC.
To: GOOGLE LLC
Reel/Frame 044101/0610 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 17, 2012
From: UNISYS CORPORATION
To: GOOGLE INC.
Reel/Frame 028060/0908 →
RELEASE OF SECURITY INTEREST Recorded Feb 29, 2012
From: DEUTSCHE BANK TRUST COMPANY AMERICAS
To: UNISYS CORPORATION
Reel/Frame 027784/0530 →
RELEASE OF SECURITY INTEREST Recorded Feb 29, 2012
From: DEUTSCHE BANK TRUST COMPANY AMERICAS
To: UNISYS CORPORATION
Reel/Frame 027784/0701 →
RELEASE OF SECURITY INTEREST Recorded Feb 29, 2012
From: DEUTSCHE BANK TRUST COMPANY AMERICAS
To: UNISYS CORPORATION
Reel/Frame 027784/0777 →
SECURITY AGREEMENT Recorded Jun 27, 2011
From: UNISYS CORPORATION
To: GENERAL ELECTRIC CAPITAL CORPORATION, AS AGENT
Reel/Frame 026509/0001 →
PATENT SECURITY AGREEMENT (JUNIOR LIEN) Recorded Oct 13, 2009
From: UNISYS CORPORATION
To: DEUTSCHE BANK TRUST COMPANY AMERICAS, AS COLLATERAL TRUSTEE
Reel/Frame 023364/0098 →
PATENT SECURITY AGREEMENT (PRIORITY LIEN) Recorded Oct 12, 2009
From: UNISYS CORPORATION
To: DEUTSCHE BANK TRUST COMPANY AMERICAS, AS COLLATERAL TRUSTEE
Reel/Frame 023355/0001 →
RELEASE BY SECURED PARTY Recorded Jul 31, 2009
From: CITIBANK, N.A.
To: UNISYS CORPORATION; UNISYS HOLDING CORPORATION
Reel/Frame 023086/0255 →
SECURITY AGREEMENT Recorded Jun 20, 2006
From: UNISYS CORPORATION; UNISYS HOLDING CORPORATION
To: CITIBANK, N.A.
Reel/Frame 018003/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 6, 2003
From: HSIEH, ERIC HAI-HSIN; SADHU, AVINASH
To: UNISYS CORPORATION
Reel/Frame 014379/0845 →