Hallo
Ich verwende in meinem Projekt MFC. Das Includen von Windows.h vor dem Includen der MFC-Header erzeugt eine Fehlermeldung.
Leider verwende ich ein API, das die Windows.h includen muss und vor dem Include noch FD_SETSIZE (die Anzahl verwendeter Sockets) definiert.
Das ist also eine ziemlich hässliche Zwickmühle. :(
Hier die Meldung vom API:
"
Programmieren - alles kontrollieren 4.934 Themen, 20.613 Beiträge
WMI Mapper
The WBEM to WMI Mapper provides a way to access WMI data from Windows platform systems. It converts incoming XML/CIM requests to Microsoft WMI requests, executes the requests, converts the results to XML/CIM and returns the results to the client. WMI Mapper receives an HTTP message containing the XML/CIM request. It decodes the XML message and extracts from the HTTP message header the user credentials provided on the connection (username and password). The WMI Mapper authenticates these credentials, verifying if the provided credentials have access to the desired WMI data. This is done because the WMI Mapper runs as a service, logged on using an account with administrative rights (which has all access to WMI data). Because of this, the WMI Mapper impersonates the user credentials provided on the HTTP message to ensure that the calling user has rights to browse WMI data. Hence, ALL requests made to the WMI Mapper MUST contain user credentials.
Ich brauche das nicht, verwende nur standard XML/CIM.
Mit dem Manual ist das so ne Sache... das kann man sich fröhlich im ganzen Netz, aus Kommentaren im Sourcecode und einigen Dateien in einem Doc Verzeichnis zusammensuchen.
Ich habe folgendes gefunden: http://www.openpegasus.org/pp/upreviews/40/324/PEP078_Authentication_Changes.htm
Zitat daraus.
... In order to enable the authentication, the user must set the define PEGASUS_WMIMAPPER on the Makefile while building the Mapper code. As this file is under the WMI Mapper specific source tree, this define is set by default.
Aber wie gesagt, ich brauche den WMI Mapper nicht.
The WBEM to WMI Mapper provides a way to access WMI data from Windows platform systems. It converts incoming XML/CIM requests to Microsoft WMI requests, executes the requests, converts the results to XML/CIM and returns the results to the client. WMI Mapper receives an HTTP message containing the XML/CIM request. It decodes the XML message and extracts from the HTTP message header the user credentials provided on the connection (username and password). The WMI Mapper authenticates these credentials, verifying if the provided credentials have access to the desired WMI data. This is done because the WMI Mapper runs as a service, logged on using an account with administrative rights (which has all access to WMI data). Because of this, the WMI Mapper impersonates the user credentials provided on the HTTP message to ensure that the calling user has rights to browse WMI data. Hence, ALL requests made to the WMI Mapper MUST contain user credentials.
Ich brauche das nicht, verwende nur standard XML/CIM.
Mit dem Manual ist das so ne Sache... das kann man sich fröhlich im ganzen Netz, aus Kommentaren im Sourcecode und einigen Dateien in einem Doc Verzeichnis zusammensuchen.
Ich habe folgendes gefunden: http://www.openpegasus.org/pp/upreviews/40/324/PEP078_Authentication_Changes.htm
Zitat daraus.
... In order to enable the authentication, the user must set the define PEGASUS_WMIMAPPER on the Makefile while building the Mapper code. As this file is under the WMI Mapper specific source tree, this define is set by default.
Aber wie gesagt, ich brauche den WMI Mapper nicht.