On Sat, 2006-04-29 at 19:40 +0200, Roland Weber wrote: > Hi Oleg, > ... > I am concerned regarding the dependencies between HttpClient and HttpAsync. > HttpAsync will need connection management, while at the same time I am > still aiming for an HttpClient that offers asynchronous functionality. > Merging HttpConn into HttpClient would introduce a recursive dependency. > However, I do not object against developing HttpConn functionality as part > of HttpClient for the time being, for the following reasons: > > - connection management functionality required by HttpAsync will have a > very different interface than for synchronous communication. I was not > sure how HttpConn and HttpAuth would relate to eachother anyway. > > - I am months away from the point where HttpAsync could make use of > connection management. Once I'm there, we can still decide how to > organize the code. For example, we can have async style connection > management implemented in HttpAsync, then consider refactoring. >
Hi Roland, It all depends how much time Mike can invest into developing and maintaining HttpConn. If not much, we should seriously consider using Commons Pool. Besides, I can well imagine HttpAsync gradually developing into a set of extensions to plain HttpClient providing support for asyncronous execution of requests and request pipelining. So, maybe dependency on HttpClient is not such a bad thing after all. Oleg > cheers, > Roland > > --------------------------------------------------------------------- > 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]
