RE: CIMXML transport compression question

"Hwang, Johnny" <[email protected]>
Newsgroups gmane.network.open-pegasus.general
Message-ID <59187A369D10D048A8A8B52B1BD1FEA507E89CE3@SACEXCMBX02-PRD.hq.netapp.com>
Lookup:

pegasus/doc/BuildAndReleaseOptions.html in your Pegasus package. 

PEGASUS_ENABLE_PROTOCOL_BINARY

Description: If true, OpenPegasus uses a faster binary protocol between local clients and the CIM server. If false, OpenPegasus uses the conventional XML-based protocol instead. See PEP#340 for more details. 
Default Value: false
Recommended Value (Development Build): false
Recommended Value (Release Build): false
Required: No
Considerations: This option improves performance by using a faster binary protocol between local clients and the CIM server.
-----
There might be a couple of other similar options, so feel free to peruse the options available.

Hope this helps,
Johnny

-----Original Message-----
From: Shane [mailto:[email protected]] 
Sent: Friday, June 15, 2012 2:56 PM
To: [email protected]
Subject: CIMXML transport compression question

Hi,

I was wondering if there is any way to have CIMOM clients request that CIMXML traffic over the connection be compressed?
I see there is a 'setRequestAcceptLanguages' and 'setRequestContentLanguages'
in the CIMClient API. But apparently no way to set the 'AcceptEncodings' or 'ContentEncodings' http headers.

Is there another way I can achieve this? Like maybe adding the WS-Management layer on top and hoping that openwsman support compression, even if the SOAP msg is larger?

The reason behind this is to conserve bandwidth over satellite connections, and there being the potential for very chatty indications being sent.


Thanks,
Shane.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.