Method and system for interfacing components via aggregate components formed by aggregating the components each with an instance of a component manager

• US 5,517,645 A
• Filed: 11/05/1993
• Issued: 05/14/1996
• Est. Priority Date: 11/05/1993
• Status: Expired due to Term

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Stutz, David S., Westin, Chris T.
• Primary Examiner(s): Oberley, Alvin E.
• Assistant Examiner(s): BACKENSTOSE, JONATHAN
• Application Number:
  US08/147,683
• Time in Patent Office: 921 Days
• Field of Search: 375/650, 375/DIG. 1, 375/DIG. 2, 395/650, 395/700, 364/280, 364/281.3, 364/281.4, 364/284, 364/284.3
• US Class Current: 719/316
• CPC Class Codes: G06F 9/449 Object-oriented method invocation or resolution

Abstract

A method and system for managing the connection of client components to an interface implemented by a server component. In a preferred embodiment, a user component provides an implementation of an interface and a description of the interface. A component manager aggregates the user component into itself to form a server component. When a client requests a connection to the interface, the component manager retrieves a reference to the interface from the user component and sends the reference to the client components. In a preferred embodiment, the component manager tracks the client components connected through an interface. A user component may also provide multiple interfaces to client components which the component manager also tracks.

Claims

1. A method in a computer system for managing interconnecting a first component to a second component, the first component having a first interface for providing services, the second component having a second interface for providing services, the method comprising the computer implemented steps of:

aggregating the first component into a first instance of a component manager and aggregating the second component into a second instance of the component manager;

under control of the first instance of the component manager,

receiving from the first component a pointer to the first interface;

receiving a request to instantiate a connector object for the first interface; and

in response to receiving the request, instantiating a first connector object and storing in the first connector object the pointer to the first interface;

under control of the second instance of the component manager,

receiving from the second component a pointer to the second interface;

receiving a request to instantiate a connector object for the second interface; and

in response to receiving the request, instantiating a second connector object and storing in the second connector object the pointer to the second interface; and

upon receiving a request to connect the first connector object to the second connector object,

retrieving from the first connector object the pointer to the first interface and storing the retrieved pointer to the first interface in the second component, whereby the second component can access the services of the first interface through the pointer to the first interface stored in the second component; and

retrieving from the second connector object the pointer to the second interface and storing the retrieved pointer to the second interface in the first component, whereby the first component can access the services of the second interface through the pointer to the second interface stored in the first component.

2. A computer-based component manager for managing the interconnection of components comprising:

an aggregator for aggregating a first user component into an instance of the component manager to form a first aggregate component, the first user component providing a first user component interface;

a retrieving module for retrieving frown the first user component an identification of the first user component interface, a pointer to the first user component interface, and a reference to a location in the first user component at which to store a pointer to a second user component interface of a second user component in a second aggregate component, the second aggregate component being an aggregate of a second instance of the component manager and the second user component;

a sending module for sending to the second aggregate component, in response to a request to connect the first aggregate component to the second aggregate component, the pointer to the first user component interface of the first user component; and

a receiving module for receiving from the second aggregate component the pointer to the second user component interface of the second user component and is for storing the received pointer to the second user component interface in the location of the first user component indicated by the retrieved reference

wherein the first aggregate component is connected to the second aggregate component by using the sending module of the first aggregate component send to the second aggegate component the pointer to the first user component interface and by using the receiving module of the first aggregate component to receive the pointer to the second user component interface and to store the received as pointer in the location of the first user component indicated by the reference retreived by the retrieving module of the first user component interface, and

wherein the first user component accesses the second user component interface using the stored pointer.

3. The component manager of claim 2 wherein the retrieving module retrieves from the first user component pointers to a plurality of user component interfaces so that connections can be established to the first user component through each of the plurality of user component interfaces of the first user component.

4. The component manager of claim 2 wherein the sending module sends the pointer to the first user component interface to a plurality of second aggregate components so that connections can be established with each of the plurality of second aggregate components through the first user component interface.

5. The component manager of claim 2 including a multicasting stub for controlling accessing of a second user component interface of each of a plurality of second aggregate components connected through the first user component interface, the second user component interfaces being provided by each of a plurality of second user components.

6. The component manager of claim 2 wherein the pointer to the first user component interface is a pointer to a first user component interface stub, the first user component interface stub for binding to the first user component interface and replacing the pointer stored by the receiving module with the pointer to the first user component interface.

7. The component manager of claim 2 wherein the first user component provides a plurality of user component interfaces and including an enumerator for enumerating the plurality of user component interfaces provided by the first user component.

8. The component manager of claim 2 wherein the first aggregate component is connected to a plurality of second aggregate components and including an enumerator for enumerating the plurality of second aggregate components.

9. The component manager of claim 2 wherein the first user component is itself an aggregate component of a child user component and an instance of the component manager and the first user component interface is provided by the child user component.

10. A method in a computer system for interconnecting two components, the method comprising the computer-implemented steps of:

creating a first component by aggregating a first instance of a component manager with a first user component, the component manager for managing the interconnection of components, the first user component having a first user component interface;

creating a second component by aggregating a second instance of the component manager with a second user component;

under control of the first instance of the component manager, creating a first connector object, the first connector object having a pointer to the first user component interface;

under the control of the second instance of the component manager, creating a second connector object having a reference to a location in the second user component; and

connecting the first component to the second component by specifying the first connector object and the second connector object, by retrieving the pointer to the first user component interface from the first connector object, by retrieving the reference to the location in the second user component from the second connector object, and by storing the retrieved pointer in the referenced location

wherein the second user component can access services of the first user component interface through the pointer stored at the referenced location.

11. The method of claim 10 wherein the second user component has a second user component interface and the second connector object has a pointer to the second user component interface, wherein the first connector object has a reference to a location in the first user component, and wherein the step of connecting includes connecting by retrieving the reference to the location in the first user component from the first connector object, by retrieving the reference to the location in the first user component from the first connector object, and by storing the retrieved pointer in the referenced location,

wherein the first user component can access service of the second user component interface through the pointer stored at the referenced location.

12. The method of claim 10 wherein the first connector object includes an identification of the first user component interface and the second connector object contains an identification of the second user component interface and the step of connecting includes determining whether the identification of the first user component interface is compatible with the identification of the second user component interface.

13. The method of claim 10 wherein the step of creating a first connector object includes the step of invoking a create call back routine of the first user component to notify the first user component of the creating of file first connector object.

14. The method of claim 10 wherein the step of connecting the first component to the second component further includes the steps of:

requesting that the first connector object connect to the second connector object;

after requesting the first connector object to connect to the second connector object, requesting the second connector object to connect to the first connector object and to notify the second user component of the connection; and

after requesting the second connector object to connect to the first connector object, requesting the first connector object to notify the first user component of the connection.