Hi Paul,

I'm the other developing committer from HttpCore. Oleg
will surely share his thoughts later this week, when he
gets back from holidays.
We are currently working on the new version of HttpClient.
You can think of HttpClient as a more comfortable API on
top of HttpCore. Our focus is on a comfortable blocking
API, since that is what most users want and also what we
need in order to obsolete the 3.x version of HttpClient.
However, if Synapse has good ideas about a comfortable
non-blocking API which we could put on top of HttpCore,
please let us know. If we should even get code contributions,
we will surely redirect some of our development time to
reviews. Though it would be a lot of work for Synapse as
well, it is probably less work than developing an all-new
HTTP framework from scratch as in your option a.

I don't know MINA myself, but Oleg does and he has taken
care that HttpCore-NIO should be easy to run on top of
MINA. That's why I recommend that you don't develop a
new HTTP framework. Even if it might seem that you save
some effort now by implementing a "good enough" solution,
you will eventually run into the same kind of problems
that we have seen with HttpClient over the years. There
are good reasons for the many classes and interfaces in
HttpCore.

Regarding AsyncWeb vs. HttpCore, I believe your analysis
is correct. If you're willing to sacrifice the memory,
AsyncWeb will give you the more mature platform. On the
other hand, HttpComponents is still being shaped, so you
have a greater influence on the direction it takes.

On a side note, there was some discussion regarding AsyncWeb
on the legal-discuss@ mailing list in the last weeks. It
seems that AsyncWeb might become an Apache project if the
lawyers can sort out their understanding of the Apache license.
http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200612.mbox/[EMAIL 
PROTECTED]

cheers,
  Roland



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to