Electrical computers and digital processing systems: multicomput – Computer-to-computer data routing – Least weight routing
Reexamination Certificate
1998-09-21
2002-10-01
Courtenay, III, St. John (Department: 2151)
Electrical computers and digital processing systems: multicomput
Computer-to-computer data routing
Least weight routing
C709S241000
Reexamination Certificate
active
06460089
ABSTRACT:
FIELD OF THE INVENTION
This invention relates generally to operating systems, and more particularly to a management console that uses snap-ins to provide management functionality.
BACKGROUND OF THE INVENTION
In the development of new operating systems, significant emphasis has been put on providing improved flexibility in the configuration and extensibility of functionality without compromising the integrity of interface and administration of the operating system. Independent software vendors are encouraged to develop their own modules that can be integrated with the operating system to provide various functionality while retaining the feel and look of a uniform user interface.
One example of software developed with such emphasis in mind is the management console of the recent version of the Windows NT operating system by Microsoft Corporation. The management console is a common console framework for management applications. The management console itself does not supply any management behavior, but instead provides a common environment for software modules commonly called “snap-ins” that may be designed by independent software vendors (ISVs). The snap-ins define the actual management behavior available to an administrator through the management console. The management console organizes and coordinates the snapins and provides an integrated user interface through which the administrator can invoke the snap-ins to provide their respective management behavior.
The flexibility and extensibility of the management console is significantly enhanced by allowing the inclusion of snap-ins called “extension snap-ins” that extend the functionality of other existing snap-ins. In order to provide its extension functionality, an extension snap-in has to be given information of the context in which the snap-in to be extended has been invoked. For example, a Computer Management snap-in may be invoked to provide information about a computer, and an Event Logs snap-in may extend the functionality of the Computer Management snap-in by providing views of the event logs of that computer. Before the Event Logs snap-in can provide the log views, it has to know which computer is being looked at by the Computer Management snap-in.
The open architecture of the management console, however, makes it difficult to require or implement direct communication between the snap-in being extended and the extension snap-in for passing context information. Not only that the snap-ins involved may be designed by different ISVs; they may also be developed at different times. Thus, the snap-in being extended may not know how the extension snap-ins want to extend its functionality or even the existence of such extension snap-ins. It would not be feasible to require that a snap-in be modified to handle the passing of context information every time a new extension snap-in is added to the management console to extend its functionality. Moreover, the use of any non-standardized ways to pass context information between snap-ins would tend to compromise the integrity and manageability of the management console. There is therefore a need for a uniform way to pass context information from a snap-in to be extended to an extension snap-in that does not require the former to have any knowledge about the latter. Such a way to pass context information should not only be simple and efficient in operation but also be easy to implement by the developers of snap-ins.
SUMMARY OF THE INVENTION
In accordance with the present invention, there is provided a method and system that provides a uniform way to pass context information from an extended snap-in of a management console to an extension snap-in to enable the extension snap-in to provide extension functionality. The extension snap-in is recorded in a registry as intended to extend the functionality of the extended snap-in. When the extended snap-in is selected to provide its management functionality, it generates a data object that carries the context information. This data object is then passed to the extension snap-in. The extension snap-in obtains the context information from the data object and provides extension functionality according to the context information.
The advantages of the invention will become apparent with reference to the following detailed description when taken in conjunction with the drawings in which:
REFERENCES:
patent: 5903728 (1999-05-01), Semenzato
patent: 5913037 (1999-06-01), Spofford et al.
patent: 5983228 (1999-11-01), Kobayashi et al.
patent: 6006279 (1999-12-01), Hayes
patent: 6026440 (2000-02-01), Shrader et al.
patent: 6154744 (2000-11-01), Kenner et al.
patent: 6167404 (2000-12-01), Morcos et al.
patent: 6173289 (2001-01-01), Sonderegger et al.
patent: 6192405 (2001-02-01), Bunnell
Microsoft Corporation,Microsoft Management Console: Snap-In User Interface Guidelines,1997.
Burggraaf S. David
Jacoby Derek
Newman Jonathan S.
Plastina Daniel
Romano Anthony C.
Courtenay III St. John
Leydig , Voit & Mayer, Ltd.
Microsoft Corporation
Nguyen Van H.
LandOfFree
Method and system for extending functionality of a... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Method and system for extending functionality of a..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Method and system for extending functionality of a... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-2972976