Hi Roland, This great! It does a wonderful job of illustrating the process and the overall design looks awesome.
Regarding the red vs. cyan question. There are only 3 differences between the two that I can see: preprocessing, postprocessing, and consume body. For consuming the body I would lean towards the HttpAsync side, since this step is necessary for maintaining the internal connection pool. For pXXprocessing, either seems fine to me. I guess it really depends on the specifics of what's happening in these two steps. If there is lots of client code being used then it should happen on the application side, if not then I would lean towards HttpAsync. I would say that for these three items it shouldn't be a huge deal on which side they go. Given the way this is put together it should be easy to change this behavior by customizing the request dispatcher or perhaps even with a built in configuration parameter. Mike On 5/28/06, Roland Weber <[EMAIL PROTECTED]> wrote:
Hi all, I have completed a first version of the wiki page on the HttpAsync design: http://wiki.apache.org/jakarta-httpclient/HttpAsyncThreadingDesign I will later add details about the use of background threads in dispatcher implementations, but I want to gather some feedback on the design level first. In particular, I'm interested in your opinion on the red vs. cyan design question. The current implementation is based on the red design. Note: as all communication on this mailing list, this request for review is addressed to _everyone_, not just to the usual suspects. If you have a view, please share it with us. Rationales are welcome, but not required. 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]
