On Fri, 2013-02-08 at 18:26 -0500, Jean-Marc Spaggiari wrote: > > From my personal experience a decent blocking HTTP client can be > > expected to outperform a decent non-blocking HTTP client by 50 to 100%, > > but such a massive difference does look very suspicious. My guess, > > though, that the way pages are being processed can be a limiting factor > > more more than the way they are being retrieved. How do you parse / > > process the content of the pages? Is your processing code based on > > standard java InputStream APIs? > > Hi Oleg, > > Is the something better to use than the standard InputStream API to > process the respons? >
You see, it is not a matter of 'better' or 'worse'. InputStream API is still being used by an overwhelming majority of parsers and content processing libraries. The trouble is that InputStream is inherently blocking. If you use an async HTTP client to retrieve content and some library based on InputStream API to process it, you pretty much lose all the advantages of asynchronous data transfer. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
