Re: CIMXML transport compression question

Thanks Johnny, unfortunately that only appears to affect local clients,
whereas my clients would be on different machines.

Thanks,
Shane.


On 6/15/12 3:01 PM, "Hwang, Johnny" <[email protected]> wrote:

>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.
>
>



Confidentiality Notice:  The information contained in this electronic e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and is confidential and/or privileged. If you and we have a confidentiality agreement or other non-disclosure obligations between us, this Notice shall be deemed to mark and identify the content of this email and any attachments as confidential and proprietary.   If any reader of this communication is not the intended recipient, unauthorized use, disclosure or copying is strictly prohibited, and may be unlawful.  If you have received this communication in error, please immediately notify the sender by return e-mail, and delete the original message and all copies from your system.  Thank you.

IRS Circular 230 Disclosure: To ensure compliance with requirements imposed by the IRS, please be advised that any U.S. federal tax advice contained in this communication (including any attachments) is not intended or written to be used or relied upon, and cannot be used or relied upon, for the purpose of (i) avoiding penalties under the Internal Revenue Code, or (ii) promoting, marketing or recommending to another party any transaction or matter addressed herein.

E-mail is susceptible to data corruption, interception, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.