Contained command invocation framework

• US 8,352,971 B2
• Filed: 07/26/2011
• Issued: 01/08/2013
• Est. Priority Date: 07/27/2007
• Status: Active Grant

• Current Assignee: Composite Ideas, LLC
• Original Assignee: Composite Ideas, LLC
• Inventors: Marsala, Paul, Babadaglian, Edwin
• Primary Examiner(s): Ho, Andy
• Application Number:
  US13/191,114
• Publication Number:
  US 20120023192A1
• Time in Patent Office: 532 Days
• Field of Search: 719/330
• US Class Current: 719/330
• CPC Class Codes: G06F 9/548 Object oriented; Remote method invocation [RMI] non-remote method invocation G06F9/449
• CPC Class Codes: H04L 67/00 Network arrangements or protocols for supporting network services or applications user-to-user messaging H04L51/00; network arrangements, protocols or services for supporting real-time applications in data packet communications networks H04L65/00

Abstract

An object-oriented middleware framework for use in a network having a plurality of hosts including a first host having an associated first memory and first processor; and a second host having an associated second memory and second processor. The object-oriented middleware framework includes an Originator Command Container instantiating a Command by executing computer programming code stored in the first memory using the first processor. The framework also includes an Invocator Command Container, remote from the Originator Command Container and its associated first host where the instantiated Command is invoked, locally by executing computer programming code stored in the second memory using the second processor.

Claims

1. A file transfer framework system, comprising:

an originator creating on a first computer a first command for pushing a file and a second command for pulling the file;

a first invocator invoking the first command locally on a second computer remotely from where the command was created; and

a second invocator invoking the second command locally on a third computer remotely from where the command was created;

wherein the first and second commands are dispersed to the second and third computers, respectively;

invocation is carried out local to the second and third computers;

the first and second commands have programmatically generic invocation triggers to the second and third computers, respectively; and

the file is transferred from the second computer to the third computer.

2. The system of claim 1 wherein the first command pushes the file to a buffer and the second command pulls the file from the buffer.

3. The system of claim 2 wherein the buffer is a socket.

4. The system of claim 1 wherein before being dispersed the first and second commands are configured on the first computer at least by providing them with information related to the file.

5. An object-oriented middleware framework system, comprising:

a first computer;

a first command container on the first computer, the first command container creating a command and configuring the command on the first computer;

wherein the command comprises functions for making a computer perform an action;

the command is dispersed to a second command container on a second computer;

the command is invoked and carried out on the second computer remotely from where the command was created;

the first command container receives a notification from the command after the command'"'"'s invocation; and

the command has a programmatically generic invocation trigger to the second computer.

6. The system of claim 5 wherein invocation of the command on the second computer is decoupled from or asynchronous to the first computer.

7. The system of claim 5 wherein the command comprises an application of bundled commands.

8. The system of claim 5 wherein the first computer redistributes the command to the second computer, the redistributed command having updated functionality but substantially the same invocation trigger.

9. The system of claim 5 wherein the first command container comprises an originator.

10. The system of claim 5 wherein the second command container comprises an invocator.

11. The system of claim 5 wherein the command relates to file transfer.

12. The system of claim 5 wherein the command relates to file synchronization.

13. The system of claim 5 wherein invocation occurs upon receipt of the dispersed command.

14. The system of claim 5 wherein invocation occurs at a predetermined time after receipt of the dispersed command.

15. The system of claim 5 wherein the notification comprises an exception, a response and/or an event.

16. The system of claim 5 wherein the first and second computers are in electronic communication with each other over the Internet.

17. The system of claim 5 wherein the first and second computers comprise the same computer.

18. The system of claim 5 wherein the second computer comprises a plurality of computers and the first computer disperses the command to the plurality of computers.

19. An object-oriented middleware framework system, comprising:

an originator creating a command on a first computer; and

an invocator invoking the command locally on a second computer but remotely from where the command was created;

wherein the command is dispersed to the second computer for invocation;

the invocation is carried out local to the second computer; and

the command has a programmatically generic invocation trigger to the second computer.

20. The system of claim 19 wherein the command relates to file transfer.

21. The system of claim 19 wherein the command relates to file synchronization.