Works for me. Mike
On 6/19/06, Oleg Kalnichevski <[EMAIL PROTECTED]> wrote:
On Mon, 2006-06-19 at 16:15 +0200, Roland Weber wrote: > Hi Oleg, > ... > I am strongly in favor of having separate release cycles for > HttpClient and HttpAsync. Here are some reasons: > > HttpClient has a more steady development cycle. I'm working > on HttpAsync only in short, intensive bursts every few months. > At least as far as coding is concerned. My job can require > customer related travel on short notice. Since my development > environment is not portable, I can't work on HttpAsync during > the week at such times, and I might need the weekends to take > care of other things. I'd hate to be the reason why a combined > release is late. > > I expect HttpClient to reach both alpha and beta stage long > before HttpAsync does. In particular the API freeze with the > beta is an issue here. There is no point in freezing the > HttpAsync API prematurely, nor in delaying the HttpClient > API freeze because of HttpAsync. While the async interfaces may > stabilize quite fast, the API includes more than just those. > > I expect HttpAsync to initially be buggier (or less stable). > At the same time, it appeals to a much smaller community. > I don't want to cut a new release for full HttpClient just to > have some bugs fixed or features added for the HttpAsync users. > Sounds reasonable. If I get a nod from Odi and Mike and no one else raises an objection I'll go ahead and set up a Jira project for HttpAsync Cheers 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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
