Hello Nicolas, > BTW, I need to asynchronously get a lot of URLs (using pipelining if > posible), HTTPAsync seems the right thing to use, but everybody points > at HTTPClient. What do I do?
Sorry to say, but HttpAsync is in a very early stage of development. My progress this year was much slower than I had hoped for. If you want to use something now, you can use the stable HttpClient 3.x or go with the HttpCore 4.0 alpha. Neither provides built-in pipelining support. We have refactored the connections in HttpCore to the point that they can be used for pipelining, so if you're willing to handle the gory details of multithreading and of request dispatching and of associating the incoming responses with the correct requests, you're welcome. We wouldn't mind some feedback on our code either. If I should make good progress, we may have a SimplePipeliningDispatcher over a single connection in a few months. But so far, progress was always slower then I had hoped for, and work on HttpCore has a higher priority than on HttpAsync. The SimpleHttpDispatcher is already asynchronous, but not pipelining. It will see a little refactoring and configurability soon. You could use it with multiple instances if you're prepared to do the request dispatching across the instances yourself. The upgrade path to the simple pipelining version would be smooth, but you have to expect API changes. HttpAsync is still a long way even from alpha. And I don't expect to have a non-simple dispatcher, that is one that uses more than one connection, ready this year. cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
