svn commit: lorikeet r250 - in trunk/white-papers/dcom: .

jelmer at jelmer at
Tue Apr 12 01:10:48 GMT 2005

Author: jelmer
Date: 2005-04-12 01:10:46 +0000 (Tue, 12 Apr 2005)
New Revision: 250


Some clarifications on WMI


Modified: trunk/white-papers/dcom/dcom.bib
--- trunk/white-papers/dcom/dcom.bib	2005-04-11 01:34:10 UTC (rev 249)
+++ trunk/white-papers/dcom/dcom.bib	2005-04-12 01:10:46 UTC (rev 250)
@@ -103,3 +103,7 @@
 	URL = {}
+ at article{COMWMI,
+	URL = { }

Modified: trunk/white-papers/dcom/dcom.tex
--- trunk/white-papers/dcom/dcom.tex	2005-04-11 01:34:10 UTC (rev 249)
+++ trunk/white-papers/dcom/dcom.tex	2005-04-12 01:10:46 UTC (rev 250)
@@ -473,13 +473,13 @@
 Distributed Management Task Force (DMTF). 
 One of the parts of WBEM is the Common Information Model (CIM) \cite{CIM}, 
-which is a standard that allows multiple parties to exchange system 
-management information.
+which is a data model for various types of management information.
-WMI is built on top of DCOM; it looks like implementing WMI will be 
-possible by implementing a thin layer of DCOM classes with 
-OpenPegasus OpenPegasus\cite{OpenPegasus}, an open source implementation 
-of WBEM, on top.
+WMI is built on top of (D)COM\cite{COMWMI}; it looks like implementing WMI 
+will be possible by implementing a thin layer of (D)COM classes. For the 
+client-side, this should be sufficient. For the server side, 
+using the OpenPegasus \cite{OpenPegasus} backend might be an option, 
+though this would probably require a lot of integration work.

More information about the samba-cvs mailing list