Ryan Hoegg wrote:
[snip]
> Some specific HTTP/1.1 features that should be included are chunking,
> compression, authentication, and cookies. I am only talking about a
> client here; our server should strictly follow the spec. This doesn't
> necessarily rule out compression, incidentally.
The s
John Wilson wrote:
>Chunking, whilst a very nice feature, is explicitly forbidden by the XML-RPC
>spec. (http://www.xml-rpc.com/spec see the Header Requirements section -
>"The Content-Length must be specified and must be correct").
>
>We already do some things which are explicitly forbidden by t
XmlRpcClientLite has a built-in "light" HTTP client implementation, which
I presume is supposed to be lighter than the Apache or Sun HTTPClient.
Headers themselves won't be that useful if you can't do something with
them on the server side so there must be something analogous to read them
of
Ryan Hoegg wrote:
> [EMAIL PROTECTED] wrote:
[snip]
> The best I have been able to find in Apache's software for a java HTTP
> Server component is in Tomcat: the Catalina connector package. In my
> current project, the XML-RPC server I am using already supports (and
> in fact requires!) HTTP/1.1
[EMAIL PROTECTED] wrote:
>If the intent is for the HTTP client component by the Apache group to be
>the single entry point on the client side, I'm all for it. It has been
>tedious to maintain two sets of similar changes between XmlRpcClient and
>XmlRpcClientLite. While the interceptors patch ma
If the intent is for the HTTP client component by the Apache group to be
the single entry point on the client side, I'm all for it. It has been
tedious to maintain two sets of similar changes between XmlRpcClient and
XmlRpcClientLite. While the interceptors patch may be large, the patch I
poste
