Hi, Sorry if this should've been posted to the user list. I'm interested in knowing the basis for the following statement on this page: http://jakarta.apache.org/httpcomponents/http-nio.html
"NIO model proved inferior to the classic IO model in terms of raw performance for blocking HTTP implementations that is where the content is meant to be produced / consumed using standard java.io.OutputStream / java.io.InputStream interfaces such as Servlet API. HttpNIO will provide an event driven, non-blocking implementation of HTTP protocol for those use scenarios where raw throughput is less important than ability to handle a significant number of simultaneous HTTP connections in a resource efficient manner." I ask because I have implemented a variety of HTTP client logic for spiders and page fetchers (in java.io, java.nio, or Python's asyncore), and I've seen a variety of results based on the implementation. Do folks have benchmarks and example code that show the relative merits of different approaches they've tried? Thanks, Garth --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
