----- Original Message ----- From: "Hannes Wallnoefer" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, February 13, 2002 10:49 AM Subject: Re: XmlRpcServer found un-streamy
> 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 (as long as HTTP keep-alive is disabled, because with keep-alive > the client needs Content-Length to know when it has read the whole > response). If this is the case, I think it would be a good idea to offer > methods for an optional stream-based interface to XmlRpcServer. It's one of the few things the spec is clear on. Personally I hate it but I think it would be unwise to break the spec. (especially in a prestigious implementation like the Apache one). Does the HTTP spec *require* Content-Length with keep-alive? If you are sending well formed XML you can tell when the response has ended without it. John Wilson The Wilson Partnership http://www.wilson.co.uk
