OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg-as4 message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [ebxml-msg-as4] compression indicator


Title: Re: [ebxml-msg-as4] compression indicator
If you feel that including the flag within the PayloadInfo is useful,  I am not militantly opposed. I can agree on this point.

Regards,
Ric


On 11/30/08 12:20 AM, "Durand, Jacques R." <JDurand@us.fujitsu.com> wrote:

I see 2 advantages in what may indeed *seem* redundant:
- adding this knowledge at ebms packaging level adds more flexibility in the ebms processing: although compression is here an "add-on" service for AS4, an eb Handler implementation could control it more easily (e.g. delay decompression until delivery while logging the message compressed) if indicated in header.
- if compression  evolves as an ebms  core "payload service" in a future version it will very likely be indicated in the PayloadInfo element. For example, we may not want the MSH to *always* decompress all
application/gzip mime parts: in some cases they could be delivered as is (e.g. if the Consumer is a temporary persistence in a queuing system, a log or an XML server)

- jacques


From: Ric Emery [mailto:remery@us.axway.com]
Sent: Thursday, November 27, 2008 4:40 AM
To: Durand, Jacques R.; ebxml-msg-as4@lists.oasis-open.org
Subject: Re: [ebxml-msg-as4] compression indicator


I would say the “Compressed” property is redundant. But, I do not necessarily have a problem with the redundancy if it is helpful.

-Ric


On 11/27/08 4:09 AM, "Durand, Jacques R." <JDurand@us.fujitsu.com> wrote:

Should we make the  compression indicator at higher level than just MIME  COntent-Type?

 "The content type of the  compressed attachment MUST be "application/gzip": this is an indicator to the  receiver that compression has been used."
 
It seems appropriate to   - also - indicate this at a higher level, in the eb header, where we  also give other encoding details on the  part:
 
    <eb:PartInfo href=""cid=foo@example.com
 <outbind://11/cid=foo@example.com> " <mailto:cid=foo@example.com <mailto:cid=foo@example.com> >  >
        <eb:PartProperties>
            <eb:Property  name="MimeType">application/xml</eb:Property>
            <eb:Property  name="CharacterSet">utf-8</eb:Property>
            <eb:Property  name="Compressed"/>
      </eb:PartProperties>
    <eb:PartInfo
 
-jacques




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]