Re: Performance Issues with Transfer-Encoding chunked
Roland Weber wrote: vzs64 wrote: Interpret the exceptions and fix the cause. Most likely, the server doesn't like what you are sending. What do you mean by along with the page? The server is a public website not under my control. I didn't say you should fix the server. Fix what you are sending there until it doesn't reply with exceptions anymore. cheers, Roland My question was more generic issue of performance with ChunkedInputStream which was also discussed in a thread earlier ' Performance issues in ChunkedInputStream - Tony Thompson Apr 11, 2007; 06:59am'. Any temporary workaround's available, or we need to wait till HttpClient 4.0? Regards vzs64 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Performance-Issues-with-Transfer-Encoding-chunked-tp14106574p14239394.html Sent from the HttpClient-User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Performance Issues with Transfer-Encoding chunked
On Sun, 2007-12-09 at 07:17 -0800, vzs64 wrote: Roland Weber wrote: vzs64 wrote: Interpret the exceptions and fix the cause. Most likely, the server doesn't like what you are sending. What do you mean by along with the page? The server is a public website not under my control. I didn't say you should fix the server. Fix what you are sending there until it doesn't reply with exceptions anymore. cheers, Roland My question was more generic issue of performance with ChunkedInputStream which was also discussed in a thread earlier ' Performance issues in ChunkedInputStream - Tony Thompson Apr 11, 2007; 06:59am'. Any temporary workaround's available, Just disable chunk-coding. or we need to wait till HttpClient 4.0? Why wait? Chunk-coding has been completely re-written for HttpClient 4.0 already. Get the latest public release of HttpClient 4.0, try executing the same request using it and see if that makes any difference. Oleg Regards vzs64 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Performance Issues with Transfer-Encoding chunked
Any suggestions for improving performance welcome. The server is sending exceptions alongwith the page, any other way to reduce download time other than writing to WebMaster of the site. -- View this message in context: http://www.nabble.com/Performance-Issues-with-Transfer-Encoding-chunked-tf4928640.html#a14157626 Sent from the HttpClient-User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Performance Issues with Transfer-Encoding chunked
Hello, Transfer-Encoding and Content-Encoding are two completely separate things. I'm pretty sure that Content-Encoding:gzip is sent with Transfer-Encoding:chunked. If you want server responses with content compression, send a header to that effect in your request, and decompress the response accordingly. There is example code for HttpCore at [1]. You can generate a wire log [2] to see what data is sent and received. Depending on the logging framework you use, you can also get timestamps for the log entries which will show where the delay happens. Feel free to post wire logs to this mailing list if you need help with interpreting them. cheers, Roland [1] http://svn.apache.org/repos/asf/jakarta/httpcomponents/httpcore/trunk/contrib/src/main/java/org/apache/http/contrib/compress/ [2] http://jakarta.apache.org/httpcomponents/httpclient-3.x/logging.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
