Re: Additional MIME headers

[Matthew MacKenzie <matt@xmlglobal.com>]

Group,
It might be prudent to place an extra, optional element into the 
ebXMLHeader to hold the extra headers in the off chance
they are useful (maybe not crucially useful).  A messaging server may 
use the mime headers to set things like server version,
time when the messaging layer accepted the message and other such minor 
vendor enhancements.

Example:

Server: FooCom_ebXML_SRV/1.1.2
M-Receipt_Time: 20011222T230333.12

would be...
<ebXMLHeader>
...
<MIMEExtraInfo>
    <Server>FooCom_ebXML_SRV/1.1.2</Server>
    <M-Receipt_Time>20011222T230333.12</M-Receipt_Time>
</MIMEExtraInfo>

...
</ebXMLHeader>

Of course, the server could just read the extra mime headers itself and 
do something with it, but having them in
the header would cut down overhead for those who want this data.

Cheers,

Matt

Burdett, David wrote:

> Folks-
> 
> What do you think the behavior of a MSH should be if it receives a message
> with additional MIME headers that are not specified in the ebXML specs.
> Possible actions are:
> 1. Ingore them, or
> 2. Report an error.
> 
> Thoughts?
> 
> DAvid
> 
> Product Management, Commerce One
> 4400 Rosewood Drive, Pleasanton, CA 94588, USA
> Tel: +1 (925) 520 4422 (also voicemail); Pager: +1 (888) 936 9599 
> mailto:david.burdett@commerceone.com; Web: http://www.commerceone.com
> 
> 
>