System and method for reducing user-application interactions to archivable form

• US 20040098729A1
• Filed: 09/15/2003
• Published: 05/20/2004
• Est. Priority Date: 09/16/2002
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: ClearCube Technology Incorporated
• Inventors: Thornton, Barry W., Enright, Todd John, Husain, Syed Mohammad Amir
• Granted Patent: US 7,430,616 B2
• Time in Patent Office: Days
• US Class Current: 719/314
• CPC Class Codes: G06F 11/1662 the resynchronized component or unit being a persistent storage device re-synchronization of failed mirror storage G06F11/2082; rebuild or reconstruction of parity RAID storage G06F11/1008
• CPC Class Codes: G06F 11/202 where processing functionality is redundant redundant communication control functionality G06F11/2005, redundant storage control functionality G06F11/2089
• CPC Class Codes: G06F 11/203 using migration
• CPC Class Codes: G06F 11/2033 switching over of hardware resources
• CPC Class Codes: G06F 11/2038 with a single idle spare processing component
• CPC Class Codes: G06F 11/2097 maintaining the standby controller/processing unit updated initialisation or re-synchronisation thereof G06F11/1658 and subgroups
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: H04L 12/1818 Conference organisation arrangements, e.g. handling schedules, setting up parameters needed by nodes to attend a conference, booking network resources, notifying involved parties
• CPC Class Codes: H04L 41/0803 Configuration setting
• CPC Class Codes: H04L 41/0813 characterised by the conditions triggering a change of settings
• CPC Class Codes: H04L 41/0816 the condition being an adaptation, e.g. in response to network events
• CPC Class Codes: H04L 41/0856 by backing up or archiving configuration information
• CPC Class Codes: H04L 41/0859 by keeping history of different configuration generations or by rolling back to previous configuration versions
• CPC Class Codes: H04L 41/0863 by rolling back to previous configuration versions
• CPC Class Codes: H04L 41/0879 Manual configuration through operator
• CPC Class Codes: H04L 41/0886 Fully automatic configuration
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: H04L 41/5009 Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
• CPC Class Codes: H04L 41/5067 Customer-centric QoS measurements
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression
• CPC Class Codes: H04L 67/02 : based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1001 : for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/10015 : Access to distributed or replicated servers, e.g. using brokers
• CPC Class Codes: H04L 67/104 : Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1048 : Departure or maintenance mechanisms
• CPC Class Codes: H04L 67/1068 : Discovery involving direct consultation or announcement among potential requesting and potential source peers
• CPC Class Codes: H04L 67/1097 : for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/133 : Protocols for remote procedure calls [RPC]
• CPC Class Codes: H04L 67/34 : involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/565 : Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/568 : Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/62 : Establishing a time schedule for servicing the requests
• CPC Class Codes: H04L 69/08 : Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/328 : in the presentation layer [OSI layer 6]
• CPC Class Codes: H04L 69/329 : in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 : Network security protocols

Abstract

Systems and methods are disclosed for a distributed computing infrastructure on a computer network comprising a plurality of computers. The distributed computing infrastructure (DCI) provides a software platform for creating, running, and managing distributed applications. DCI may include XML-capable software applications on a peer-to-peer network. DCI may include small, network-unaware applications called peerlets. DCI may include a system and method for creating complex distributed applications using pre-complied binaries. DCI may include a capability for multiple, independent collaborative sessions for distributed collaborative applications (e.g., chat, instant messaging, shared whiteboard, etc.). DCI may include systems and methods for reducing interactions between users and applications to archivable form and then playing back the interactions. DCI may include a system and method for automatic software retrieval on a peer-to-peer network.

Claims

1. A method comprising:

entering user input to a source application on a first computer system to request performance of a task;

performing the task in response to the user input;

generating a message in response to the user input, wherein the message comprises one or more instructions which are computer-executable to perform the task, and wherein the message comprises metadata which comprise identifying characteristics of the source application;

translating the message from an original format to a portable format on the first computer system, thereby generating a portable message; and

storing the portable message in a message log.

2. The method of claim 1, further comprising:

retrieving the portable message from the message log; and

executing the one or more instructions to perform the task again.

3. The method of claim 1, further comprising:

retrieving the portable message from the message log; and

executing the one or more instructions to perform the task on one or more additional computer systems.

4. The method of claim 1, wherein the message log comprises a queue.

5. The method of claim 1, further comprising:

sorting the message log by one or more elements of the metadata.

6. The method of claim 1, further comprising:

sorting the message log by application type of the source application.

7. The method of claim 1, further comprising:

sorting the message log by message sender.

8. The method of claim 1, further comprising:

sorting the message log by message recipient.

9. The method of claim 1, further comprising:

sending the portable message from the first computer system to a second computer system using peer-to-peer message passing between the first computer system, the second computer system, and optionally one or more intermediary computer systems; and

performing the requested task on the second computer system.

10. The method of claim 9, further comprising:

routing the portable message to a target application on the second computer system based on the metadata.

11. The method of claim 1,

wherein the portable format comprises XML, and wherein the portable message comprises an XML message.

12. A carrier medium comprising program instructions, wherein the program instructions are computer-executable to implement:

receiving user input at a source application on a first computer system to request performance of a task;

performing the task in response to the user input;

generating a message in response to the user input, wherein the message comprises one or more instructions which are computer-executable to perform the task, and wherein the message comprises metadata which comprise identifying characteristics of the source application;

translating the message from an original format to a portable format on the first computer system, thereby generating a portable message; and

storing the portable message in a message log.

13. The carrier medium of claim 12, wherein the program instructions are further computer-executable to implement:

retrieving the portable message from the message log; and

executing the one or more instructions to perform the task again.

14. The carrier medium of claim 12, wherein the program instructions are further computer-executable to implement:

retrieving the portable message from the message log; and

executing the one or more instructions to perform the task on one or more additional computer systems.

15. The carrier medium of claim 12,

wherein the message log comprises a queue.

16. The carrier medium of claim 12, wherein the program instructions are further computer-executable to implement:

sorting the message log by one or more elements of the metadata.

17. The carrier medium of claim 12, wherein the program instructions are further computer-executable to implement:

sorting the message log by application type of the source application.

18. The carrier medium of claim 12, wherein the program instructions are further computer-executable to implement:

sorting the message log by message sender.

19. The carrier medium of claim 12, wherein the program instructions are further computer-executable to implement:

sorting the message log by message recipient.

20. The carrier medium of claim 12, wherein the program instructions are further computer-executable to implement:

sending the portable message from the first computer system to a second computer system using peer-to-peer message passing between the first computer system, the second computer system, and optionally one or more intermediary computer systems; and

performing the requested task on the second computer system.

21. The carrier medium of claim 20, wherein the program instructions are further computer-executable to implement:

routing the portable message to a target application on the second computer system based on the metadata.

22. The carrier medium of claim 12,

wherein the portable format comprises XML, and wherein the portable message comprises an XML message.

23. A system comprising:

a CPU;

a memory which is coupled to the CPU, wherein the memory stores program instructions which are executable by the CPU to;

receive user input at a source application to request performance of a task;

perform the task in response to the user input;

generate a message in response to the user input, wherein the message comprises one or more instructions which are computer-executable to perform the task, and wherein the message comprises metadata which comprise identifying characteristics of the source application;

translate the message from an original format to a portable format on the first computer system, thereby generating a portable message; and

store the portable message in a message log.

24. The system of claim 23, wherein the program instructions are further executable by the CPU to:

retrieve the portable message from the message log; and

execute the one or more instructions to perform the task again.

25. The system of claim 23, wherein the program instructions are further executable to:

retrieve the portable message from the message log; and

execute the one or more instructions to perform the task on one or more additional computer systems.

26. The system of claim 23,

wherein the message log comprises a queue.

27. The system of claim 23, wherein the program instructions are further executable by the CPU to:

sort the message log by one or more elements of the metadata.

28. The system of claim 23, wherein the program instructions are further executable by the CPU to:

sort the message log by application type of the source application.

29. The system of claim 23, wherein the program instructions are further executable by the CPU to:

sort the message log by message sender.

30. The system of claim 23, wherein the program instructions are further executable by the CPU to:

sort the message log by message recipient.

31. The system of claim 23, wherein the program instructions are further executable to:

send the portable message to a second computer system using peer-to-peer message passing between a first computer system, a second computer system, and optionally one or more intermediary computer systems; and

perform the requested task on the second computer system.

34. The system of claim 23,

wherein the portable format comprises XML, and wherein the portable message comprises an XML message.

33. The system of claim 32, wherein the program instructions are further executable to:

route the portable message to a target application on the second computer system based on the metadata.