Hi Oleg,
It's true that we have agreed [1] on 1.3 for HttpCore and 1.4 for NIO.
So it makes sense to put the NIO code into a separate code directory.
That the NIO code will be small in size, doesn't come as a surprise to
me. And I absolutely agree that it doesn't make sense to put it under a
separately release cycle.
hack on
Odi
[1]
http://wiki.apache.org/jakarta-httpclient/HttpClientApiRedesign?action=recall&rev=30
Oleg Kalnichevski wrote:
Folks,
I have started working on NIO extensions to HttpCore. So far it looks
like there will be fairly little code involved and there will be
virtually no changes to the protocol layer of HttpCore required. This
leads me to believe that HttpNIO as a separate module with an separate
release cycle does not actually make any sense.
My Evil(tm) Plan is to introduce an additional module to HttpCore SVN
project in order to keep Java 1.4 dependent NIO extensions separate from
the rest of HttpCore that requires Java 1.3 only. Maven2 fully support
multi-module projects and conditional compilation based on JDK version.
This way Java 1.3 could still compile a fully functional Java 1.3
version HttpCore without NIO extensions.
What do you think?
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
[web] http://www.odi.ch/
[blog] http://www.odi.ch/weblog/
[pgp] key 0x81CF3416
finger print F2B1 B21F F056 D53E 5D79 A5AF 02BE 70F5 81CF 3416
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
