On Jul 21, 2006, at 4:24 AM, Oleg Kalnichevski wrote:
MINA may be a good choice for architectures that aim at supporting a
wide range of network protocols. As far as HttpComponents are
concerned,
we are not going to expand the scope of the project beyond HTTP.
So, in
my opinion, the benefits of having an abstract I/O layer provided by
MINA does not outweigh the cost of an extra dependency.
I understand that POV.. Just means that you'll have to do all of the
NIO plumbing that's required inside of the HttpComponents project
itself.
Moreover, it should be feasible to put HttpCore (and potentially
HttpNIO) on top of MINA or any other I/O abstraction layer by
providing
a custom implementation of the HttpDataReceiver and
HttpDataTransmitter
interfaces and to re-use higher level protocol logic of
HttpComponents.
Certainly. At a minimum, I would hope that we would be able to share
higher level code like that, and sounds like that's one point we are
already in agreement on :)
-pete
--
[EMAIL PROTECTED] - http://fotap.org/~osi
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
