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


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-cppa message

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

Subject: Re: Transport level compression

Arvola Chan wrote:
> HTTP allows transport level compression through the use of the
> Content-Encoding entity-header. The permissible compression
> algorithms include gzip, compress, and deflate.
> Should the use of transport level compression be specifiable in
> the CPA when the transport is HTTP?
> Thanks,
> -Arvola
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>


This is an interesting question. I would say that this is probably
a good idea. However, we shouldn't limit to Content-Encoding.
Seems to me that what a CPP/A should define (at least for HTTP)
is equivalent to the HTTP Accept* request headers that a client
uses for HTTP requests to inform the origin server what its
capabilities and/or preferences are.

It also seems to me that one could apply the Accept headers
abstractly to any transport protocol. Thus, something like:

<c:Transport transportId=".." xmlns:c="...">
	<c:SendingProtocol version="1.1">HTTP</c:SendingProtocol>
	<c:SendingProtocol version="1.1">SMTP</c:SendingProtocol>
	<c:ReceivingProtocol version="1.1">HTTP</c:ReceivingProtocol>
	<c:Accept c:mediaType="..."/> <!-- zero or more -->
	<c:AcceptEncoding c:contentCoding="..."/> <!-- zero or more -->
	<c:AcceptLanguage xml:lang="..."/> <!-- zero or more -->
	<c:AcceptCharset charset="..."/> <!-- zero or more -->



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

Powered by eList eXpress LLC