|Publication number||USRE41706 E1|
|Application number||US 11/331,418|
|Publication date||Sep 14, 2010|
|Filing date||Jan 13, 2006|
|Priority date||Nov 30, 1999|
|Also published as||US6678743|
|Publication number||11331418, 331418, US RE41706 E1, US RE41706E1, US-E1-RE41706, USRE41706 E1, USRE41706E1|
|Inventors||Graham W. Glass, Chris K. Wensel|
|Original Assignee||Glass Graham W, Wensel Chris K|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (99), Non-Patent Citations (43), Classifications (15), Legal Events (6)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present invention relates in general to object-oriented technologies and more particularly to a method for moving objects in a distributed computing environment.
In object oriented programming, real world objects are modeled by software objects that have encapsulated therein special procedures and data elements. In object-oriented programming terminology, procedures are referred to as methods. To avoid having to redefine the same methods and data members for each and every occurrence of an object, object-oriented programming provides the concept of classes. An inherent structure of one or more levels of increasingly more specialized classes is created to provide templates that define the methods and variables to be included in the objects of each class. The classes at the lower levels of the inheritance structure inherit the behavior, methods, and variables of the classes above. Classes above a certain class in an inheritance structure are referred to as parent classes setting up a parent-child relationship. Therefore, an object belonging to a class is a member of that class, and contains the special behavior defined by the class. In this manner, each object is an instance of a defined class or template and the need to redefine the methods and data members for each occurrence of the object is eliminated.
One example of an object-oriented programming language is Java, developed by Sun Microsystems. To define a class in Java, the programmer creates a .java file containing the source code to define the class. The .java file is compiled to create a .class file containing the executable code to define the class. Instances of the class file are instantiated to create an object containing data and methods defined by the .class file.
Object-oriented programming is a method of programming that abstracts a computer program into manageable sections. The key to object-oriented programming is the concept of encapsulation. Encapsulation is a method by which the subroutines, or methods, that manipulate data are combined with the declaration and storage of that data. This encapsulation prevents the data from arbitrarily being accessed by other programs' subroutines, or objects. When an object is invoked, the associated data is available and can be manipulated by any of the methods that are defined within an object to act upon the data.
The basic component of encapsulation is a class. A class is an abstraction for a set of objects that share the same structure and behavior. An object is a single instance of a class that retains the structure and behavior of the class. Objects also contain methods that are the processes by which an object is instructed to perform some procedure or manipulation of data that it controls. Classes may also be characterized by their interface which defines the elements necessary for proper communication between objects.
Often, a programmer needs to add functionality to an existing class of objects but either does not want to change the existing .class file or does not have access to the source code and, therefore, does not have the ability to alter the source code. In addition, the programmer may not want to alter the functionality of the existing .class file since a .class file may be used in more than one application program. Therefore, it is desirable to add functionality to an existing class of objects during the execution of an application program without altering the associated source code.
Distributed computing allows an object on one computer system to seamlessly communicate with and manipulate an object contained in a second computer system when the two computer systems are connected by a computer network. The second computer system may also be referred to as another address space. Client/server systems are an example of this type of distributed computing system. Sophisticated distributed computing systems have removed the communications burden from the computer programs, or objects in an object oriented programming environment, and placed it in a mid-level operating system that manages communications across a computer network to facilitate a client's access to and manipulation of data contained on a server system. The server system could be a computer in a different address space and remote to a user on a client system.
In distributed processing environments, objects in different address spaces may exchange a large number of messages. Using traditional distributed processing communications techniques may lead to slow response time and increased network traffic. Moving a first object to the same address space as a second object makes communications between the two objects local and, therefore, reduces network traffic. Local messages are often at least one thousand times faster than remote messages sent through the distributed computing system.
From the foregoing, it may be appreciated that a need has arisen for a method for moving objects in a distributed computing environment. In accordance with the present invention, an improved method for moving objects in a distributed computing environment is provided that substantially eliminate or reduce disadvantages and problems associated with conventional methods for moving objects in a distributed computing environment.
According to an embodiment of the present invention, there is provided a method for moving objects in a distributed computing system that includes receiving a move indication at a mobility object. The mobility object is aggregated with the primary object through an aggregate object located at a current host address and port number. The move indication instructs the mobility object to move the primary object to a new host address and port number. The aggregate object has the primary object as a primary facet object and the mobility object has as a facet object.
The method then creates a serialized version of the mobility object in response to the move indication. The method then sends the serialized version of the mobility object to the new host address and port number and creates a new version of the mobility object at the new host address and port number from the serialized version of the mobility object. The method then creates a serialized version of the primary object in response to a serialize and move message received from the new version of the mobility object. The method then sends the serialized version of the primary object to the new host address and port number and creates a new version of the primary object at the new host address and port number from the serialized version of the primary object. The method then creates a new aggregate object with the new version of the primary object as a new primary facet object and the new version of the mobility object as a new facet object at the new host address and port number.
The present invention provides various technical advantages over conventional methods for moving objects in a distributed computing environment. For example, one technical advantage is providing a method for objects that exchange a large number of messages to move to a common computer to reduce the amount of time needed for communications and to conserve system resources. Other technical advantages may be readily apparent to one skilled in the art from the following figures, description, and claims.
For a more complete understanding of the present invention and the advantages thereof, reference is now made to the following description taken in conjunction with the accompanying drawings, wherein like reference numbers represent like parts, in which:
Aggregate object 14 is an aggregation of one or more facet objects 28 within an object-oriented environment. Aggregate object 14 and the associated facet objects 28 function as a single logical object within the object-oriented environment. A change to one of the facet objects 28 creates a logical change in the other facet objects 28 and aggregate object 14. For example, if one of the facet objects 28 moves to a different processing environment, or address space, the aggregate object 14 to which the particular facet object 28 is linked and any other associated facet objects 28 will move as a single logical object to the new, processing environment, or address space. Primary facet objects 16, first facet object 20, and second facet object 24 represent a group of one or more facet objects 28.
Each aggregate object 14 communicates directly with its associated set of facets 32. Each facet within a set of facets 32 is linked to a particular facet object 28. Each facet in the set of facets 32 contains basic information related to its associated facet object 28 to facilitate use of the aggregate object 14 within application program 12. The information contained in each facet in the set of facets 32 for its associated facet object 28 includes the class of the facet object 28 and any interfaces implemented by the facet object 28. In one embodiment, each facet in set of facets 32 is a proxy object created from the associated facet object 28. The proxy object is created by using Java Reflection to determine a particular facet object's 28 name, class, and interfaces. This information is then packaged into a facet in set of facets 32. The particular facet in set of facets 32 is an object that includes the name, class, and interfaces for the associated facet object 28. An interface in an object oriented environment defines the format and information needed to communicate with a particular object. An interface may be referred to as the public view of the object.
During application program development, the software developer may utilize aggregate objects 14 to extend the functionality of existing objects without modifying source code. The software developer extends functionality of an existing object by placing it in an aggregate object 14 as the primary facet object 16 and aggregating additional objects within aggregate object 14 as facet objects 28. Within application program 12, a particular object may be the primary facet object 16 of only one aggregate object 14. Each aggregate object 14 in application program 12 will have a unique primary facet object 16. In one embodiment, a software developer desires to extend the functionality of a specified object to add additional functions such as mobility within a distributed processing environment or the ability to function as an agent within a distributed processing environment. Another example of adding functionality to an existing object would be adding repair history to a car object or adding a bonus plan to an employee object.
The software developer dynamically creates an aggregate object 14 with the specified object as the associated primary facet object 16. The term “dynamically” is used here to refer to using program statements during execution of application program 12 to create aggregate object 14. The software developer then dynamically adds first facet object 20 and second facet object 24 to aggregate object 14. First facet object 20 and second aggregate object 24 provide additional functionality for primary facet object 16. Any method of any facet object 28 may affect all facet objects 28 within aggregate object 14. Therefore, invoking a method on first facet object 20 will effect a change in primary facet object 16.
Application program 12 may create and utilize one or more aggregate objects 14. Each aggregate object 14 has one or more associated facet objects 28. Facet objects 28 may be added and deleted as application program 12 progresses depending upon processing requirements. To access a particular facet object 28, application program 12 may request access to the particular facet object 28 that extends the functionality of a primary facet object 16 by requesting a class or interface using commands that invoke facet control module 30. Facet control module 30 then scans the set of facets 32 associated with the aggregate object 14 identified in the facet control system command until locating the particular facet object 28 that has a class that equals or extends the requested class or implements the requested interface. Facet control module 30 returns a reference to the first facet in the set of facets 32 that has a class that equals or extends the requested class or implements the requested interface. Application program 12 can then invoke the particular facet object 28 by using the returned reference to the facet in the set of facets 32. In another embodiment, facet control system 30 may return a list of all facets within the set of facets 32 with associated facet objects 28 that have a class that equal or extend the requested class or implement the requested interface. Application program 12 can then determine which facet object 28 in the returned reference list to invoke.
If no facet object 28 exists that has a class that equals or extends the requested class or implements the requested interface, a not-found condition is returned to application program 12 as a null reference. Application program 12 can then determine whether a new aggregate object 14 should be created, whether an object should be added to an existing aggregate object 14 as an additional facet object 28, or whether appropriate error handling procedures should be performed.
In system 40, application program 12, facet control module 30, aggregate object 14, set of facets 32 and primary facet object 16 all exist within a first environment 42. First facet object 20 exists within a second environment 44. Communications between aggregate object 14 and first facet object 20 are facilitated by using an appropriate distributed processing system such as an object request broker. In one embodiment, a first facet object proxy 46 resides in first environment 42 and is logically coupled to first facet object 20 in second environment 44. First facet object proxy 46 may be a conventional proxy object created from first facet object 20. First facet object proxy 46 has an interface 47 modeled on first interface 22. Interface 47 has a format and needed information similar to first interface 22. Second facet object 24 resides in a third environment 48. Communications between aggregate object 14 and second facet object 24 are facilitated by using an appropriate distributed processing system such as an object recognition broker. In one embodiment, a second facet object proxy 50 resides in first environment 42 and provides communications between aggregate object 14 and second facet object 24. Second facet object proxy 50 may be a conventional proxy object created from second facet object 24. Second facet object proxy 50 has an interface modeled on second interface 26. Interface 51 has a format and needed information similar to second interface 26.
In one embodiment, the following syntax may be used to create an aggregate object 14:
Facets myFacets=new Facets (myPrimary);
where myPrimary identifies an existing object which will become primary facet object 16 within the newly created aggregate object 14 identified as myFacets. Facet control module 30 creates an aggregate object 14 identified as myFacets. Next, facet control module 30 creates a primary facet 34 identified as primaryFacet. Primary facet 34 is linked to aggregate object 14. Next, facet control module 30 creates a primary facet object 16 identified as myPrimary. Primary facet object 16 is linked to primary facet 34. Facet control module 30 creates primary facet 34 such that primary facet 34 contains the class of primary facet object 16 and the interfaces implemented by primary facet object 16.
myfacets.get (“class name”);
where myfacets.get identifies the aggregate object 14 (myfacets) and the operation (get) for class/interface finder 76. The class name in the above example may also identify a requested interface name. The method proceeds to step 124 where a facet reference is set to aggregate object's 14 primary facet, primary facet 34. Primary facet 34 should be the first facet in the set of facets 32.
The method proceeds to decisional step 125 where class/interface finder 76 determines if the facet referenced by facet-reference has a class that equals the requested class, has a class that extends the requested class, or implements the requested interface. If the facet in the set of facets 32 identified by the facet-reference meets one of the above tests, the Yes branch of decisional step 125 proceeds to step 126 where class/interface finder 76 returns a reference to the facet in the set of facets 32 identified by the facet-reference. The method proceeds to step 128 where application program 12 uses the returned reference to identify the facet object 28 through the reference to a facet in the set of facets 32. Application program 12 then invokes the facet object 28. After step 128, the method terminates.
Returning to decisional step 125, if the facet in the set of facets 32 identified by the facet-reference does not meet one of the aforementioned tests, the No branch of decisional step 125 proceeds to decisional step 130 where class/interface finder 76 determines whether aggregate object 14 has more facets within its associated set of facets 32. If the set of facets 32 includes more facets, the Yes branch of decisional step 130 proceeds to step 132 where the facet-reference is set to the next facet, first facet 36 in this example, in the set of facets 32 associated with aggregate object 14. The method returns to decisional step 125 to process the next facet identified by the facet-reference.
Returning to decisional step 130, if the set of facets 32 associated with aggregate object 14 does not include more facets, the No branch of decisional step 130 proceeds to step 134 where a null reference is returned. Application program 12 would then perform appropriate error processing upon receipt of the null reference. After step 134, the method terminates.
myFacets.of (“class name”);
where the desired aggregate object 14 is identified (myFacets) and the desired operation is also identified (.of). “Class name” refers to an existing .class file. When adding facet objects to aggregate object 14, class names should be used so that an instance of the class may be generated and added to aggregate object 14 as a facet object 28.
The method proceeds to step 154 where the method of
The method proceeds to decisional step 156 where a determination is made regarding whether a null reference was returned. If a null reference was not returned, the No branch of decisional step 156 proceeds to step 158 where the reference received from step 126 in the method of
Returning to decisional step 156, if a null reference is received, the Yes branch of decisional step 156 proceeds to step 160 where object adder 72 creates an instance of the requested class. The method proceeds to step 162 where object adder 72 creates a new facet for the instance of the requested class. Object adder 72 creates the new facet by adding the requested class and the interfaces implemented by that class to the new facet. The new facet is an object that summarizes available information regarding the associated facet object that in this example is the created instance of the requested class. The new facet becomes a member of the set of facets 32 associated with the aggregate object 14.
The method proceeds to step 164 where object adder 72 links the instance of the requested class created in step 160 to the new facet created in step 162. The method proceeds to step 166 where object adder 72 links the new facet created in step 162 to the aggregate object 14. The method proceeds to step 168 where a reference to the new facet created in step 162 is returned. After step 168, the method terminates.
In one embodiment, the facets.of command that is used to add objects to an existing aggregate object 14 may be used by software developers when they have determined that a requested class should be part of aggregate object 14 but they are not sure that the requested class has been added to facet objects 28 that are associated with aggregate object 14. By using this type of command, the software developer requests a facet object 28 that has a class that equals or extends a requested class and is guaranteed that a reference to a facet object 28 will be returned.
In addition to the above-referenced sample commands, one embodiment of the present invention includes the following command to determine the primary facet object 16 of aggregate object 14:
myFacets.getPrimary ( );
where the desired aggregate object 14 is identified as myFacets and the desired operation is identified as getPrimary. The sample command returns a reference to primary facet object 16.
Another sample command from one embodiment of the present invention includes the following command to determine the members of set of facets 32 associated with aggregate object 14;
myFacets.getFacets ( );
where the desired aggregate object 14 is identified as myfacets and the desired operation is identified as getfacets. The sample command returns a list of each facet object 28 associated with aggregate object 14.
Object deleter 74 of facet control module 30 provides a software developer with the ability to delete a specified object from facet objects 28. The software developer identifies the particular facet object 28 to be removed from aggregate object 14 and instructs facet control module 30 to remove the specified facet object from aggregate object 14. Object deleter 74 physically deletes the associated facet in set of facets 32 and removes the link between the specified facet object and aggregate object 14. If the specified facet object has no remaining references, an operating system of the object oriented environment may remove the specified facet object from the object oriented environment during a garbage collection procedure.
An object may be made mobile within a distributed processing environment by defining the object as a primary facet object 16 linked to an aggregate object 14 and aggregating a mobility object as a second facet object 24 as previously described. To move an object from one address space to another address space, a mobility method is invoked within aggregate object 14. As previously described, aggregate object 14 then locates the facet without one or more facet objects 28 that provides the requested method. The mobility method may be invoked directly on the mobility facet object. In that case, the mobility facet object informs the aggregate object that the mobility method has been invoked. In another embodiment, the functionality of mobility is built into the object. To cause that object to move from one address space to another address space, a mobility method is invoked on the object.
The movement process begins in
In response to move indication 224, the move operation continues in
The move operation continues in
The move operation continues at
The move operation continues at
The move operation continues at
Messages that were blocked by lock object 230 are released and forwarded as necessary to new host address and port number 234 as discussed in detail with relation to
The forwarding operation continues at
Reference holder 302 receives message MSG and determines that it is a remote message. In one embodiment, a remote message is determined by comparing the host address of the object originating the message with the host address of the reference holder 302. After determining that message MSG2 is a remote message, reference holder 302 throws an “object moved” exception to object 310. Object 310 catches the “object moved” exception and resends message MSG2 to new host address and port number 316 identified in the “object moved” exception. All future messages from object 310 are sent directly to object 314 at new host address and port number 316. By using the “object moved” exception, messages destined for a target object do not pass through an intermediate host address thereby making communications between objects more efficient.
After new aggregate group 244 registers at new host address and port number 234 but prior to aggregate group 200 disconnecting its component parts, a post-departure callback notification may be sent to primary facet object 204. At this point, the component parts of aggregate group 200 are considered stale since a new active aggregate group 244 exists at new host address and port number 234. The post-departure callback notification allows aggregate group 200 to perform internal final processing before its component parts are delinked and garbage collected and prior to unblocking any messages at current host address and port number 222.
Thus, it is apparent that there has been provided in accordance with the present invention, a method for moving objects in a distributed computing environment that satisfies the advantages set forth above. Although the present invention and its advantages have been described in detail, it should be understood that various changes, substitutions, and alterations may be readily apparent to those skilled in the art and may be made herein without departing from the spirit and the scope of the present invention as defined by the following claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5325524||Apr 6, 1992||Jun 28, 1994||Digital Equipment Corporation||Locating mobile objects in a distributed computer system|
|US5341478||Nov 3, 1993||Aug 23, 1994||Digital Equipment Corporation||Methods and apparatus for providing dynamic invocation of applications in a distributed heterogeneous environment|
|US5396630||Oct 6, 1992||Mar 7, 1995||International Business Machines Corporation||Method and system for object management across process boundries in a data processing system|
|US5432924||Dec 15, 1993||Jul 11, 1995||Microsoft Corporation||Method and system for selectively applying an appropriate object ownership model|
|US5481721||Oct 31, 1994||Jan 2, 1996||Next Computer, Inc.||Method for providing automatic and dynamic translation of object oriented programming language-based message passing into operation system message passing using proxy objects|
|US5511197||Nov 29, 1993||Apr 23, 1996||Microsoft Corporation||Method and system for network marshalling of interface pointers for remote procedure calls|
|US5577251||Nov 7, 1995||Nov 19, 1996||Sun Microsystems, Inc.||Object oriented system for executing application call by using plurality of client-side subcontract mechanism associated with corresponding plurality of server-side subcontract mechanism|
|US5603031||Jul 8, 1993||Feb 11, 1997||General Magic, Inc.||System and method for distributed computation based upon the movement, execution, and interaction of processes in a network|
|US5619710||Jun 22, 1994||Apr 8, 1997||Digital Equipment Corporation||Method and apparatus for object-oriented invocation of a server application by a client application|
|US5634010||Oct 21, 1994||May 27, 1997||Modulus Technologies, Inc.||Managing and distributing data objects of different types between computers connected to a network|
|US5655101||May 27, 1994||Aug 5, 1997||International Business Machines Corporation||Accessing remote data objects in a distributed memory environment using parallel address locations at each local memory to reference a same data object|
|US5724503||Mar 31, 1995||Mar 3, 1998||Sun Microsystems, Inc.||Method and apparatus for interpreting exceptions in a distributed object system|
|US5737607||Sep 28, 1995||Apr 7, 1998||Sun Microsystems, Inc.||Method and apparatus for allowing generic stubs to marshal and unmarshal data in object reference specific data formats|
|US5745703||Jul 18, 1995||Apr 28, 1998||Nec Research Institute, Inc.||Transmission of higher-order objects across a network of heterogeneous machines|
|US5778227||Aug 1, 1995||Jul 7, 1998||Intergraph Corporation||System for adding attributes to an object at run time in an object oriented computer environment|
|US5781633||Jul 1, 1996||Jul 14, 1998||Sun Microsystems, Inc.||Capability security for transparent distributed object systems|
|US5787175||Oct 23, 1995||Jul 28, 1998||Novell, Inc.||Method and apparatus for collaborative document control|
|US5793965||Mar 22, 1995||Aug 11, 1998||Sun Microsystems, Inc.||Method and apparatus for determining the type of an object in a distributed object system|
|US5812781||Sep 5, 1995||Sep 22, 1998||Telefonaktiebolaget Lm Ericsson||System for routing incoming connection-less messages to processes which are already handling messages from same source node|
|US5812793||Jun 26, 1996||Sep 22, 1998||Microsoft Corporation||System and method for asynchronous store and forward data replication|
|US5822585||May 30, 1997||Oct 13, 1998||Compuware Corporation||System and method for cooperative processing using object-oriented framework|
|US5848419||May 21, 1997||Dec 8, 1998||Sun Microsystems, Inc.||Methods and apparatus for providing transparent persistence in a distributed object operating environment|
|US5862325||Sep 27, 1996||Jan 19, 1999||Intermind Corporation||Computer-based communication system and method using metadata defining a control structure|
|US5867665||Mar 24, 1997||Feb 2, 1999||Pfn, Inc||Domain communications server|
|US5881230||Jun 24, 1996||Mar 9, 1999||Microsoft Corporation||Method and system for remote automation of object oriented applications|
|US5897634||May 9, 1997||Apr 27, 1999||International Business Machines Corporation||Optimized caching of SQL data in an object server system|
|US5903725||Sep 6, 1996||May 11, 1999||International Business Machines Corporation||Recoverable proxy object in an object oriented environment|
|US5928335||Oct 29, 1997||Jul 27, 1999||Ricoh Company, Ltd.||Client/server system having middleware-based interface between client and server image processing objects|
|US5956737||Sep 9, 1996||Sep 21, 1999||Design Intelligence, Inc.||Design engine for fitting content to a medium|
|US5983233||Aug 15, 1997||Nov 9, 1999||Alcatel Alsthom Compagnie Generale D'electricite||Process for managing the naming of objects, process for mapping an object name to a CORBA object reference, program module, computer unit, and computer system|
|US5987506||May 2, 1997||Nov 16, 1999||Mangosoft Corporation||Remote access and geographically distributed computers in a globally addressable storage environment|
|US5999988||Mar 31, 1997||Dec 7, 1999||Sun Microsystems, Inc.||Method and apparatus for generating and employing a run-time generated stub to reference an object in object oriented systems|
|US6006018||Oct 3, 1995||Dec 21, 1999||International Business Machines Corporation||Distributed file system translator with extended attribute support|
|US6012067||Mar 2, 1998||Jan 4, 2000||Sarkar; Shyam Sundar||Method and apparatus for storing and manipulating objects in a plurality of relational data managers on the web|
|US6012081||Jul 3, 1996||Jan 4, 2000||Siemens Aktiengesellschaft||Service and event synchronous/asynchronous manager|
|US6016393||Feb 10, 1997||Jan 18, 2000||General Magic, Inc.||System and method for distributed computation based upon the movement, execution, and interaction of processes in a network|
|US6026415||Nov 11, 1997||Feb 15, 2000||Next Software, Inc.||Transparent local and distributed memory management system|
|US6032190||Oct 3, 1997||Feb 29, 2000||Ascend Communications, Inc.||System and method for processing data packets|
|US6041166||Jul 15, 1996||Mar 21, 2000||3Com Corp.||Virtual network architecture for connectionless LAN backbone|
|US6044409||Jun 26, 1996||Mar 28, 2000||Sun Microsystems, Inc.||Framework for marshaling and unmarshaling argument object references|
|US6061740||Jul 15, 1997||May 9, 2000||Novell, Inc.||Method and apparatus for heterogeneous network management|
|US6085030||May 2, 1997||Jul 4, 2000||Novell, Inc.||Network component server|
|US6085086||Jun 27, 1997||Jul 4, 2000||Lucent Technologies Inc.||Network-based migrating user agent for personal communication services|
|US6092196||Nov 25, 1997||Jul 18, 2000||Nortel Networks Limited||HTTP distributed remote user authentication system|
|US6134591||Jun 18, 1997||Oct 17, 2000||Client/Server Technologies, Inc.||Network security and integration method and system|
|US6138235||Jun 29, 1998||Oct 24, 2000||Sun Microsystems, Inc.||Controlling access to services between modular applications|
|US6138251||Jun 30, 1997||Oct 24, 2000||Sun Microsystems, Inc.||Method and system for reliable remote object reference management|
|US6141759||Dec 10, 1997||Oct 31, 2000||Bmc Software, Inc.||System and architecture for distributing, monitoring, and managing information requests on a computer network|
|US6151639||Jun 19, 1997||Nov 21, 2000||Sun Microsystems, Inc.||System and method for remote object invocation|
|US6157960||May 7, 1997||Dec 5, 2000||International Business Machines Corporation||Technique for programmatically creating distributed object programs|
|US6178505||Mar 4, 1998||Jan 23, 2001||Internet Dynamics, Inc.||Secure delivery of information in a network|
|US6182153||Feb 15, 1996||Jan 30, 2001||International Business Machines Corporation||Object-oriented programming interface for developing and running network management applications on a network communication infrastructure|
|US6182154||Apr 7, 1997||Jan 30, 2001||International Business Machines Corporation||Universal object request broker encapsulater|
|US6182155||Jan 2, 1998||Jan 30, 2001||International Business Machines Corporation||Uniform access to and interchange between objects employing a plurality of access methods|
|US6195794||Aug 12, 1997||Feb 27, 2001||International Business Machines Corporation||Method and apparatus for distributing templates in a component system|
|US6205491||Dec 18, 1997||Mar 20, 2001||Sun Microsystems, Inc.||Method and apparatus for deferred throwing of exceptions in C++|
|US6212574||Apr 4, 1997||Apr 3, 2001||Microsoft Corporation||User mode proxy of kernel mode operations in a computer operating system|
|US6230160||Jul 16, 1998||May 8, 2001||International Business Machines Corporation||Creating proxies for distributed beans and event objects|
|US6237135||Sep 11, 1998||May 22, 2001||Borland Software Corporation||Development system with visual design tools for creating and maintaining Java Beans components|
|US6253253||Aug 25, 1997||Jun 26, 2001||International Business Machines Corporation||Method and apparatus for optimizing references to objects in a data processing system|
|US6253256||Oct 15, 1997||Jun 26, 2001||Sun Microsystems, Inc.||Deferred reconstruction of objects and remote loading in a distributed system|
|US6260078||Jul 3, 1996||Jul 10, 2001||Sun Microsystems, Inc.||Using a distributed object system to find and download java-based applications|
|US6269373||Feb 26, 1999||Jul 31, 2001||International Business Machines Corporation||Method and system for persisting beans as container-managed fields|
|US6282580||Jul 2, 1996||Aug 28, 2001||Sun Microsystems, Inc.||Bridge providing communication between different implementations of object request brokers|
|US6304918||Mar 11, 1997||Oct 16, 2001||Microsoft Corporation||Object interface control system|
|US6321275||Oct 24, 1997||Nov 20, 2001||Microsoft Corporation||Interpreted remote procedure calls|
|US6324543 *||Mar 6, 1998||Nov 27, 2001||International Business Machines Corporation||Dynamic object migration method using proxy object links to support automatic object distribution in an object-oriented environment|
|US6338089||Mar 31, 1999||Jan 8, 2002||Bull Hn Information Systems Inc.||Method and system for providing session pools for high performance web browser and server communications|
|US6343332||Mar 17, 1998||Jan 29, 2002||Fujitsu Limited||Communication link information generating device, a three-tier client/server system, and a medium storing a communication link information generator program|
|US6345382||Feb 12, 1998||Feb 5, 2002||International Business Machines Corporation||Run-time customization in object-oriented design|
|US6347341||Feb 22, 1999||Feb 12, 2002||International Business Machines Corporation||Computer program product used for exchange and transfer of data having a siga vector and utilizing a queued direct input-output device|
|US6347342||Jul 15, 1996||Feb 12, 2002||Next Software, Inc.||Method and apparatus for dynamically brokering object messages among object models|
|US6356930||Oct 15, 1999||Mar 12, 2002||Silverstream Software, Inc.||Connection concentrator for distributed object systems|
|US6374308||Apr 23, 1996||Apr 16, 2002||Sun Microsystems, Inc.||Method and apparatus for interactively connecting distributed objects to a graphic user interface|
|US6385661||Oct 19, 1998||May 7, 2002||Recursion Software, Inc.||System and method for dynamic generation of remote proxies|
|US6405246||Feb 18, 1999||Jun 11, 2002||International Business Machines Corporation||Automatic and dynamic software code management|
|US6415315||Nov 25, 1998||Jul 2, 2002||Recursion Software, Inc.||Method of moving objects in a computer network|
|US6434595 *||Nov 25, 1998||Aug 13, 2002||International Business Machines Corporation||Method of executing mobile objects and recording medium storing mobile objects|
|US6438616||Dec 18, 1997||Aug 20, 2002||Sun Microsystems, Inc.||Method and apparatus for fast, local corba object references|
|US6442620||Aug 17, 1998||Aug 27, 2002||Microsoft Corporation||Environment extensibility and automatic services for component applications using contexts, policies and activators|
|US6446084||Sep 22, 1998||Sep 3, 2002||Sun Microsystems, Inc.||Optimizing symbol table lookups in platform-independent virtual machines|
|US6453333||Jun 10, 1998||Sep 17, 2002||Lion Bioscience Ag||Research system using multi-platform object oriented program language for providing objects at runtime for creating and manipulating biological or chemical data to facilitate research|
|US6496871 *||Jun 30, 1998||Dec 17, 2002||Nec Research Institute, Inc.||Distributed agent software system and method having enhanced process mobility and communication in a computer network|
|US6513157||Nov 30, 1999||Jan 28, 2003||Recursion Software, Inc.||System and method for dynamically aggregating objects|
|US6549955||Apr 12, 2002||Apr 15, 2003||Recursion Software, Inc.||System and method for dynamic generation of remote proxies|
|US6567861||Sep 17, 1997||May 20, 2003||International Business Machines Corporation||Method and apparatus for remotely running objects using data streams and/or complex parameters|
|US6601018||Feb 4, 1999||Jul 29, 2003||International Business Machines Corporation||Automatic test framework system and method in software component testing|
|US6629128||Nov 30, 1999||Sep 30, 2003||Recursion Software, Inc.||System and method for distributed processing in a computer network|
|US6701382||Dec 23, 1998||Mar 2, 2004||Nortel Networks Limited||Name service for transparent container objects|
|US6714976||Aug 3, 1999||Mar 30, 2004||Concord Communications, Inc.||Systems and methods for monitoring distributed applications using diagnostic information|
|US6851118||Jun 27, 2000||Feb 1, 2005||Sun Microsystems, Inc.||Remote object access|
|US6931455||Nov 30, 1999||Aug 16, 2005||Recursion Software, Inc.||System and method for communications between a CORBA object request broker and a non-CORBA object request broker|
|US6947965||Nov 30, 1999||Sep 20, 2005||Recursion Software, Inc.||System and method for communications in a distributed computing environment|
|US6951021||Nov 30, 1999||Sep 27, 2005||Recursion Software, Inc.||System and method for server-side communication support in a distributed computing environment|
|US6993774||Nov 30, 1999||Jan 31, 2006||Recursion Software, Inc.||System and method for remote enabling classes without interfaces|
|US7347342||Oct 29, 2004||Mar 25, 2008||Elmar Grandy||Container for holding sterile goods and sterile goods dispenser|
|US20010003824||Mar 14, 1997||Jun 14, 2001||International Business Machines Corporation||Bootstrapping technique for distributed object client systems|
|EP0727739A1||Feb 17, 1995||Aug 21, 1996||International Business Machines Corporation||Object-oriented programming interface for developing and running network management applications on a network communication infrastructure|
|GB2326255A||Title not available|
|1||"Distribution Object Activation and Communication Protocols", IBM Technical Disclosure Bulletin, US, IBM Corp. New York, vol. 37(7), (Jul. 1, 1994),539-542.|
|2||"Final Office Action", U.S. Appl. No. 11/158,734, (Aug. 20, 2009), 18 pages.|
|3||"Improved Process for Visual Development of Client/Server Programs", IBM Technical Disclosure Bulletin, vol. 41(1), XP-000772108,(Jan. 1998),281-283.|
|4||"Java Core Reflection, API and Specification", JavaSoft, (Jan. 1997),40-47.|
|5||"Java RMI Tutorial", Revision 1.3, JDK 1.1 FCS, Sun Microsystems, (Feb. 10, 1997),1-14.|
|6||"Life Cycle Service Specification", CORBA Object Services Specification, Chp. 6, OMG, c9i.omg.org/docs/formal/97-02-11.pdf,, (Feb. 11, 1997),pp. 6-1 through 6-62.|
|7||"Non Final Action", U.S. Appl. No. 11/858,878, (Mar. 29, 2010), 30 pages.|
|8||"Non Final Offce Action", U.S. Appl. No. 11/158,734, (Feb. 19, 2010), 21 pages.|
|9||"Passing Proxies as Parameters to Methods and Return Values from Methods", IBM Technical Disclosure Bulletin, vol. 41(1), XP-000772037,(Jan. 1998),89-92.|
|10||"PCT/US99/24510", International Search Report for Appl. No. PCT/US99/24510,(Apr. 19, 2000),4.|
|11||"SOMobjects Developer's Toolkit Programmer's Guide", vol. I: SOM and DSOM, (Dec. 1996),275-276.|
|12||"The Component Object Model (DRAFT) Specification", Microsoft Corporation, Mar. 6, 1995),1-4, 39-46.|
|13||"The Component Object Model Specification", Microsoft Corporation and Digital Equipment Corporation, Chapters 1 and 2 (printed on Oct. 26, 2005 from daimi.au.dk*-datpete/COT/COM SPEC/html/com_spec.html),(Oct. 24, 1995),54.|
|14||Bent, Thomsen et al., "Mobile Agents", External Report ECRC-92-21, European Computer-Industry Research Center, (1995).|
|15||Bieszczad, A. "Towards Plug-and-Play Networks wilh Mobile Code", SCE Technical Report, (Mar. 1997),17.|
|16||Bowers, "Some Principles for the Encapsulation of The Behavior of Aggregate Objects", IEEE, (1993),6/1-6/4.|
|17||Brando, Thom "Comparing COBRA and DCE", (Mar. 1996).|
|18||Cappelo, Robert "Overview of RMI Architecture (Computer Science Online Course Notes)", University of California Santa Barbara Department of Computer Science, cs.ucsb.edu/-cappello/290i/lectures/rmi/architecture/sld001.htm,(Sep. 7, 1998).|
|19||*||Glen McCluskey, "Using Java Reflection," Jan. 1998, 6 pages.|
|20||Glen, McCluskey "Using Java Reflection", article retrieved from java.sun.com website., (Jan. 1998).|
|21||Hayton, Richard et al., "FlexiNet Architecture", (Feb. 1999),171-178.|
|22||Hayton, Richard et al., "Mobile Java Objects", (1998).|
|23||Henderson, Sellers et al., "What is This Thing Called Aggregation?", IEEE, (Jun. 1999),236-250.|
|24||Henry, E. et al., "Fine-Grained Mobility in the Emerald System", ACM, (Feb. 1998),22.|
|25||Hof, Markus "Just-in-Time Stub Generation", Proceedings of the Joint Modular Languages Conference (JMLC) 97, Linz, Austria,(Mar. 19-21, 1997),197-206.|
|26||HOP;OMG's Internet Inter-ORG Protocol, A Brief discription, printed from omg.org,(1994).|
|27||HOP;OMG's Internet Inter—ORG Protocol, A Brief discription, printed from omg.org,(1994).|
|28||Johansen, Dag et al., "An Introduction to the TACOMA Distributed System Version 1.0", Technical Report 95-23, Department of Computer Science, University of Troms, Norway, (Jun. 1995).|
|29||*||Matthew Izatt and Patrick Chan, "Ajents: Toward an Environment for Parallel, Distributed and Mobile Java Applications", Jun. 1999, pp. 1-10.|
|30||McKie, S. "Software Agents: Application Intelligence Goes Undercover", DBMS, (Apr. 1995),8.|
|31||McManis, Chuck "Take an in-depthlook at the java reflection API", retrieved from JavaWorld.com, (Sep. 1997),1-10.|
|32||Moons, H. et al., "Object Migration In a Heterogeneous World-A Multi-Dimensional Affair", IEEE, (1993),62-72.|
|33||Moons, H. et al., "Object Migration In a Heterogeneous World—A Multi-Dimensional Affair", IEEE, (1993),62-72.|
|34||Orfali, et al., "The Essentiai Distributed Objects Survival Guide", Chapter 4, Published by John Wiley & Suns, Inc., (1996),67-90.|
|35||Petrie, C. J., "Agent-based Engineering, the Web, and Intelligence", IEEE Expert, (Dec. 1996),12.|
|36||Richard Hayton and ANSA Team, "FlexiNet Architecture," Feb. 1999, p. 171-178.|
|37||Richard Hayton, Mike Bursell, Douglas Donaldson, Andrew Herbert, "Mobile Java Objects," 1998.|
|38||Robert, Gray et al., "Mobile agents for mobile computing", Technical Report PCS-TR96-285, Dept. of Computer Science, Dartmouth College,(May 1996).|
|39||Roy, Mark et al., "IChoosing between COBRA and DCOM", (Oct. 1996).|
|40||Roy, Mark et al., "Interworking COM with COBRA", (May 1996).|
|41||Spruit, Sandor "Reflections on Java, Beans, and Relational databases", retrieved from JavaWorld.com, (Sep. 1997),1-8.|
|42||Wayner, P. "Free Agents", BYTE, (Mar. 1995),7.|
|43||Wescom, et al., "The object/agent approach: A computing model for the future", Object Magazine, (Mar.-Apr. 1995),31-33.|
|U.S. Classification||719/317, 719/316, 709/202, 719/315, 709/201|
|International Classification||G06F9/44, G06F9/54|
|Cooperative Classification||G06F9/443, G06F9/4862, G06F9/4435, G06F9/4433|
|European Classification||G06F9/48C4P2M, G06F9/44F2A, G06F9/44F2B, G06F9/44F2C|
|Nov 14, 2007||AS||Assignment|
Owner name: OBJECTSPACE, INC., TEXAS
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:GUTHRIE, RHETT DAVIS;GLASS, GRAHAM W.;REEL/FRAME:020111/0822
Effective date: 19981011
|Nov 16, 2007||AS||Assignment|
Owner name: RECURSION SOFTWARE, INC., TEXAS
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:OBJECTSPACE, INC.;REEL/FRAME:020121/0928
Effective date: 20020214
Owner name: MAINLINE DATA LLC, NEVADA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:RECURSION SOFTWARE, INC.;REEL/FRAME:020121/0966
Effective date: 20050621
|Jan 11, 2011||CC||Certificate of correction|
|Jun 22, 2011||FPAY||Fee payment|
Year of fee payment: 8
|Jun 24, 2015||FPAY||Fee payment|
Year of fee payment: 12
|Nov 5, 2015||AS||Assignment|
Owner name: XYLON LLC, DELAWARE
Free format text: MERGER;ASSIGNOR:MAINLINE DATA LLC;REEL/FRAME:037053/0611
Effective date: 20150813