Vivek Pandey wrote:
>> Do you mean that the CTE header will be part of the MIME multipart
>> message? (see correct examples here [2]).
>>
>
> May be incase of SMTP, but I am not sure. [2] talks about SOAP over HTTP
> not other transports. See RFC 3023, XML Media Types,
> http://www.faqs.org/rfcs/rfc3023.html. Its not just about
> Mime/Multipart, in case that there is no multiple parts, there is only
> one part - it may apply to 7bit transports and proably we should expose
> it thru our decoders.
>
It seems to be this is an issue with getting at the bytes of the
content. So the case for HTTP Content-Encoding is similar to the case
for Content-Transfer-Encoding with other transports like SMTP.
The transport implementation should provide the Decoder with an
InputStream that is capable of decoding the bytes. Thus the Decoder does
not need to really care what the underlying encoding of the bytes are.
Paul.
--
| ? + ? = To question
----------------\
Paul Sandoz
x38109
+33-4-76188109