Hannes Wallnoefer wrote: > > Yes, this is very unefficient for large resonses. The reason for doing > it this way is that the XML-RPC says: "The Content-Length must be > specified and must be correct." So we need the whole response to be > packed before we can start sending headers. > > Now I don't think this is really needed for the XML-RPC clients out > there. Most that I'm aware of use a full HTTP client and should do fine > without
There is at least on implementation that uses the Content-length: header. My own xmlrpc-client. :-), a quick (and you may call it therefore dirty) C++ client from the times when only java implementations ruled the xmlrpc world. Of course I could update to better C++ xmlrpc-clients when I want to use newer xmlrpc-versions and I personally don't want to veto against this development trend. I just wanted to point out that implementations *exist* which really depend on particular specification details. GreetinX Steffen -- Steffen Schwigon <[EMAIL PROTECTED]>
