|
version 1.54, 2001/12/19 02:54:41
|
version 1.60, 2002/02/05 10:39:02
|
|
|
|
| CHANGE LOG FOR PEGASUS | CHANGE LOG FOR PEGASUS |
| |
|
| |
|
| |
Version 1.07 working towards 1.1 - Started 4 Feb 2002 |
| |
Started just before cutover to the new dispatcher, etc. |
| |
TAG: VERSION_1_07 |
| |
|
| |
1. KS - Updated pegsusversion to 1.07 and tagged file. |
| |
|
| |
2. (Markus Mueller) 05 Feb 2002 - AIX support. |
| |
|
| |
------------------------------------------------------------------- |
| Version 1.06 working towards 1.1 Started 13 December 2001 | Version 1.06 working towards 1.1 Started 13 December 2001 |
| | |
| 1. Merged back to Main branch. All general development will be in main branch | 1. Merged back to Main branch. All general development will be in main branch |
|
|
|
| intrinsic methods. If a parameter is specified more than once, a | intrinsic methods. If a parameter is specified more than once, a |
| CIM_ERR_INVALID_PARAMETER exception is thrown. | CIM_ERR_INVALID_PARAMETER exception is thrown. |
| | |
| |
4. (Nag Boranna - HP) 14 Jan 2002 - Created CIMOperationRequestAuthorizer queue |
| |
and moved Authorization verification code from CIMOperationRequestDecoder |
| |
queue to this new queue. Modified CIMServer.cpp to create |
| |
CIMOperationRequestAuthorizer queue only when authorization is enabled. |
| |
Also modified CIMRequestMessagesin CIMMessage.h to include userName to make |
| |
it available to the CIMOperationRequestDispatcher. |
| |
|
| |
5. (Mary Hinton - Jan 17, 2002) Fixed the problem with the CIMserver when it |
| |
runs as a Windows service. The work thread was exiting instead of running |
| |
forever. The problem was noticed when the TestClient program and CIMserver |
| |
service were both running. The service wasn't accessible to the TestClient |
| |
program. |
| |
|
| |
6. (Nitin Upasani - Jan 25, 2002) Operations on CIM_IndicationSubscription, |
| |
CIM_IndicationHandlerCIMXML and CIM_IndicationFilter classes will be now processed |
| |
in new queue, IndicationService which will get invoked from dispatcher. |
| |
CIM_CREATE_INSTANCE_REQUEST_MESSAGE |
| |
CIM_MODIFY_INSTANCE_REQUEST_MESSAGE |
| |
CIM_DELETE_INSTANCE_REQUEST_MESSAGE |
| |
CIM_GET_INSTANCE_REQUEST_MESSAGE |
| |
CIM_ENUMERATE_INSTANCES_REQUEST_MESSAGE |
| |
CIM_ENUMERATE_INSTANCE_NAMES_REQUEST_MESSAGE |
| |
|
| |
This new service will also take care of processing the indications on receiving |
| |
CIM_PROCESS_INDICATION_REQUEST_MESSAGE. This message should come from |
| |
IndicationProvider or some other mechanism which is not yet clear. |
| |
|
| |
IndicationService will also receive following messages from PG_ProviderRegistration |
| |
when a new IndicationProvider will get registered. |
| |
CIM_NOTIFY_PROVIDER_REGISTRATION_REQUEST_MESSAGE |
| |
CIM_NOTIFY_PROVIDER_TERMINATION_REQUEST_MESSAGE |
| |
|
| |
I had also defined new Indication Provider APIs, enableIndication, disableIndication |
| |
and modifyIndication with more parameters passed and eventually planning to terminate |
| |
old APIs (provideIndication, cancelIndication and updateIndication). Also there is a |
| |
plan to implement one more call as startIndication and will be done soon. |
| |
|
| |
There are three new test programs in IndicationService directory, which will create |
| |
Filter, Indication and Subscription instances using IndicationService. |
| |
|
| |
Also modified sample IndicationProvider code with the new APIs introduced. |
| |
|
| ------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
| | |
| Version 1.1.1 - 3 August 2001 - Development Branch (Work in Progress) | Version 1.1.1 - 3 August 2001 - Development Branch (Work in Progress) |
Return to
changelog.txt
CVS log
Up to [Pegasus] / pegasus / doc / Attic