Contained command invocation middleware framework

• US 8,020,177 B2
• Filed: 07/27/2007
• Issued: 09/13/2011
• 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:
  US11/829,182
• Publication Number:
  US 20090031293A1
• Time in Patent Office: 1,509 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. 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, wherein the object-oriented middleware framework comprises;

an Originator Command Container instantiating a Command by executing computer programming code stored in the first memory using the first processor; and

an Invocator Command Container, remote from the Originator Command Container and its associated first host where the Command is instantiated, locally invoking the instantiated Command by executing computer programming code stored in the second memory using the second processor;

wherein the Command is dispersed to the Invocator Command Container for invocation;

the invocation is carried out local to the Invocator Command Container; and

the Command has a programmatically generic invocation trigger such that functionality can be updated without requiring updated interfaces at the Invocator Command Container.

2. The object-oriented middleware framework in accordance with claim 1, wherein the first and second hosts are each a device that hosts a processor.

3. The object-oriented middleware framework in accordance with claim 1, wherein the Originator Command Container has an associated Applet that provides an application context for origination of the Command.

4. The object-oriented middleware framework in accordance with claim 1, wherein the Command at the Originator Command Container undergoes instantiation, configuration and dispersion.

5. The object-oriented middleware framework in accordance with claim 4, wherein the Invocator Command Container is solely charged with invocation of the Command dispersed by the Originator Command Container.

6. The object-oriented middleware framework in accordance with claim 1, wherein the Invocator Command Container provides a runtime environment for the Command to operate.

7. The object-oriented middleware framework in accordance with claim 1, wherein instruction code representing operations to be performed does not originate with the Invocator Command Container.

8. The object-oriented middleware framework in accordance with claim 7, wherein the instruction code is received by the Invocator Command Container during deployment of an Applet associated with the Originator Command Container or dynamically downloaded with the Command from the Originator Command Container.

9. The object-oriented middleware framework in accordance with claim 1, further comprising a Notification generated by the Invocator Command Container once the Command has been invoked and transmitted back to the Originator Command Container.

10. The object-oriented middleware framework in accordance with claim 9, wherein the Notification is at least one of an Exception, Response or an Event.

11. The object-oriented middleware framework in accordance with claim 1, wherein the Command functionality relates to file transfer.

12. A method for employing an object-oriented middleware framework in a network, the method comprising the steps of:

providing a first host and storing in a first memory associated with the first host computer programming code executed by a first processor associated with the first host to establish an Originator Command Container;

providing a second host and storing in a second memory associated with the second host computer programming code executed by a second processor associated with the second host to establish an Invocator Command Container;

instantiating a Command generated by the Originator Command Container using the first processor associated with the first host; and

invoking locally the Command via the Invocator Command Container using the second processor associated with the second host remotely from the Originator Command Container and its associated first host where the Command was instantiated;

wherein the Command is dispersed to the Invocator Command Container for invocation;

the invocation is carried out local to the Invocator Command Container; and

the Command has a programmatically generic invocation trigger such that functionality can be updated without requiring updated interfaces at the Invocator Command Container.

13. The method in accordance with claim 12, wherein said instantiating step further comprises the steps of:

configuring the instantiated Command at the Originator Command Container; and

dispersing the configured Command from the Originator Command Container to the Invocator Command Container.

14. The method in accordance with claim 13, wherein the Invocator Command Container is solely charged with invocation of the Command dispersed by the Originator Command Container.

15. The method in accordance with claim 12, wherein the Invocator Command Container provides a runtime environment for the Command to operate.

16. The method in accordance with claim 12, wherein instruction code representing operations to be performed does not originate with the Invocator Command Container.

17. The method in accordance with claim 16, further comprising the step of receiving the instruction code by the Invocator Command Container during deployment of an Applet associated with the Originator Command Container or dynamically downloaded with the Command from the Originator Command Container.

18. An article of manufacture comprising a computer program storage medium readable by a computer, the medium tangibly embodying one or more computer program encoded with instructions executable by the computer to perform a method for employing an object-oriented middleware framework in a network having a plurality of hosts, the method comprising the steps of:

providing a first host and storing in a first memory associated with the first host computer programming code executed by a first processor associated with the first host to establish an Originator Command Container;

providing a second host and storing in a second memory associated with the second host computer programming code executed by a second processor associated with the second host to establish an Invocator Command Container;

instantiating a Command generated by the Originator Command Container using the first processor associated with the first host; and

invoking locally the Command via the Invocator Command Container using the second processor associated with the second host remotely from the Originator Command Container and its associated first host where the Command was instantiated;

wherein the Command is dispersed to the Invocator Command Container for invocation;

the invocation is carried out local to the Invocator Command Container; and

the Command has a programmatically generic invocation trigger such that functionality can be updated without requiring updated interfaces at the Invocator Command Container.

19. The article of manufacture in accordance with claim 18, wherein the Invocator Command Container is solely charged with invocation of the Command dispersed by the Originator Command Container.

20. The article of manufacture in accordance with claim 18, wherein instruction code representing operations to be performed does not originate with the Invocator Command Container.

21. The article of manufacture in accordance with claim 20, wherein the instruction code is received by the Invocator Command Container during deployment of an Applet associated with the Originator Command Container or dynamically downloaded with the Command from the Originator Command Container.

22. A computer readable program product establishing an object oriented 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, comprising;

an Originator Command Container instantiating a Command by executing computer programming code stored in the first memory using the first processor; and

an Invocator Command Container, remote from the Originator Command Container and its associated first host where the Command was instantiated, locally invoking the instantiated Command by executing computer programming code stored in the second memory using the second processor;

wherein the Command is dispersed to the Invocator Command Container for invocation;

the invocation is carried out local to the Invocator Command Container; and

the Command has a programmatically generic invocation trigger such that functionality can be updated without requiring updated interfaces at the Invocator Command Container.

23. The computer readable program product in accordance with claim 22, wherein the Invocator Command Container is solely charged with invocation of the Command dispersed by the Originator Command Container.

24. The computer readable program product in accordance with claim 22, wherein instruction code representing operations to be performed does not originate with the Invocator Command Container.

25. The computer readable program product in accordance with claim 24, wherein the instruction code is received by the Invocator Command Container during deployment of an Applet associated with the Originator Command Container or dynamically downloaded with the Command from the Originator Command Container.

26. A method for employing an object-oriented middleware framework, the method comprising the steps of:

instantiating a Command on a first computer; and

invoking the Command locally on a second computer but remotely from where the Command was instantiated;

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 such that functionality can be updated without requiring updated interfaces at the second computer.

27. The method in accordance with claim 26, further comprising the step of configuring and dispersing the Command where it was instantiated on the first computer.