[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Compression Simple Proposal
Below is what I had in mind for compression support in AS4. I would like to keep the proposal simple - for both implementers and interoperability. As such I only propose support for one compression scheme - GZIP. And do not drastically alter the SOAP with Attachments Packaging. The scheme below should be easy to implement without needing to modify existing SOAP stacks. The ebMS processor should be able to handle the compression/decompression operations on its own. Regards, Ric Emery --------- Application payloads that are built in conformance with the SOAP Messages with Attachments [SOAPATTACH] specification may be compressed. Compression of the SOAP envelope and/or payload containers within the SOAP Body of an ebMS Message is not supported. To compress the payload(s) of a message build in conformance with the SOAP Messages with Attachments [SOAPATTACH] specification the GZIP compression algorithm MUST be used. Compression MUST be applied before payloads are attached to the SOAP Message. The content type of the compressed attachment MUST be "application/gzip". When compression, signature and encryption are required of the MSH, the message MUST be compressed prior to being signed and/or encrypted. A eb:PartInfo/eb:PartProperties/eb:Property/@name= "MimeType" value is RECOMMENDED to identify the mimetype of the payload before compression was applied. A eb:PartInfo/eb:PartProperties/eb:Property/@name= "CharacterSet" value is RECOMMENDED to identify the character set of the payload before compression was applied. Example: <eb:PartInfo href="cid=foo@example.com"> <eb:PartProperties> <eb:Property name="MimeType">application/xml</eb:Property> <eb:Property name="CharacterSet">utf-8</eb:Property> </eb:PartProperties> <eb:PartInfo>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]