version 1.74, 2002/03/07 00:46:53
|
version 1.80, 2002/03/12 00:15:45
|
|
|
18 (KS) 6 March 2002 - Implemented changes to compiler and flavors to correct the | 18 (KS) 6 March 2002 - Implemented changes to compiler and flavors to correct the |
definition of CIMFlavors. | definition of CIMFlavors. |
| |
|
|
|
19. (Roger Kumpf - HP) 1 Mar 2002 - Reworked the XmlWriter class to |
|
eliminate many of the redundant memory copies that resulted from the |
|
nested method call structure. Now, instead of having a method at |
|
each level that adds a begin tag, contents, and an end tag, there |
|
are separate methods to add the begin and end tags. At the top |
|
level, each of the begin tag methods are called, then the message |
|
"body" is added, followed by calls to the end tag methods. |
|
|
|
The message body is currently still copied twice, once into the XML |
|
payload and then again when the HTTP header is added. (Since the |
|
HTTP header contains a content length field, the header cannot be |
|
constructed until the payload is complete.) It is possible to |
|
remove these extra copies as well, but that would require additional |
|
changes elsewhere in the code. For example, the HTTPMessage class |
|
would need to hold the headers and payload separately rather than in |
|
a single buffer. |
|
|
|
Along with these changes, I did a lot of cleanup. Much of the XML |
|
formatting code has been moved from CIMReference to XmlWriter. Also, |
|
error message formatting has been consolidated in XmlWriter from the |
|
various encoders and decoders, etc. |
|
|
|
20. (Roger Kumpf - HP) 5 Mar 2002 - Added checks in the |
|
CIMOperationRequestDecoder and CIMExportRequestDecoder to validate |
|
that the information in the HTTP headers of a request is consistent |
|
with what is encoded in the XML request itself. |
|
|
|
Specifically, the CIMOperation, CIMProtocolVersion, CIMMethod, |
|
CIMObject, CIMBatch, CIMExport, and CIMExportBatch headers are |
|
validated. |
|
|
|
21. (KS) 7 March 2002 - Correct error in qualifier propagation processing in |
|
qualifierlist.resolve. Temporarily remove the DEFAULT setup on the |
|
Compiler qualifier generation. Add tests for resolve processing. |
|
|
|
22. (Roger Kumpf - HP) 8 Mar 2002 - Simplified CIMClient API construction. |
|
Previously, the client application constructed a client API using: |
|
|
|
Monitor* monitor = new Monitor; |
|
HTTPConnector* connector; |
|
connector = new HTTPConnector(monitor); |
|
Uint32 timeoutMillis = 60 * 1000; // optional |
|
|
|
CIMClient client(monitor, connector, timeoutMillis); |
|
|
|
With this change, the client application now looks like: |
|
|
|
Uint32 timeoutMillis = 60 * 1000; // optional |
|
|
|
CIMClient client(timeoutMillis); |
|
|
|
The old style allowed an SSL context to be specified in the HTTPConnector |
|
constructor. It seems that the SSL context is really a property of a |
|
connection rather than of the client API. So instead of adding an SSL |
|
context parameter to the CIMClient constructor, I added it to the CIMClient |
|
connect() method. There are now forms of the connect() method with and |
|
without an SSL context. Similar changes were made in the HTTPConnector |
|
class to allow specification of an SSL context in the connect() method |
|
rather than in the constructor. |
|
|
|
NOTE: Client applications are affected and must be updated with this |
|
change. I've already updated all the clients that are checked in and |
|
included in the Pegasus build. |
|
|
|
23. (KS) 8 March 2002 - Correct error in compiler that caused length field |
|
of fixed length arrays to be lost. |
|
|
|
24. (Jenny Yu - HP) 8 March 2002 - Modified the CIMException class to NOT |
|
include the source filename and line number in the exception message. |
|
However, for anyone who wishes to include such information in the |
|
CIM Exception message, a compile option DEBUG_CIMEXCEPTION can be used |
|
for that purpose. |
|
|
|
A couple of changes have been made to the Tracer class: |
|
|
|
- CIMException messages can now be put in a trace file using the Tracer. |
|
A new interface has been added to the Tracer to accept a CIMException |
|
as input and writes the exception message in the CIMException to the |
|
trace file. This message will include the source filename and the |
|
line number of the CIMException originator. |
|
|
|
Tracer::traceCIMException(traceComponent, traceLevel, cimException); |
|
|
|
- Strings can now be traced using the Tracer class: |
|
A new interface has been added to the Tracer to accept a String as |
|
input and writes the String to the trace file. |
|
|
|
(ex.) |
|
You can issue the following method call: |
|
Tracer::trace(TRC_CONFIG, Tracer::LEVEL2, "Operation Failed."); |
|
|
|
or use the following new macro: |
|
PEG_TRACE_STRING(TRC_CONFIG, Tracer::LEVEL2, "Operation Failed."); |
|
|
|
25. (Ramnath Ravindran - Compaq) 8 March 2002 - added IPCTru64.h and modified |
|
several files so that Pegasus could build and run on Tru64 unix. Added |
|
one macro in ConfigUnix and ConfigWindows (PEGASUS_OR_IOS_BINARY) in |
|
the case where std::ios::binary is present with a bitwise OR operator. |
|
This macro only works when the std::ios::binary is NOT the first |
|
operator to be "OR"ed. |
|
|
------------------------------------------------------------------- | ------------------------------------------------------------------- |
Version 1.06 working towards 1.1 Started 13 December 2001 | Version 1.06 working towards 1.1 Started 13 December 2001 |
| |