I think its a great idea,
Here's my 2 cents, (c) (c)
it would be great if httpComponents was the child from a larger project
like commons-net.
And all the code that is common to smtp, http, ftp, irc, etc.... could
go in the commons-net layer.
I use http client all the time, and i occasionally need the ftp/smtp/irc
protocol, it would be nice if
all this stuff was in the same place to plug it in easier :) and of
course to avoid code/method duplication
across various projects all working on the same issues...... like if
the httpComponenets project
improves socket timeout handeling (or some other basic network layer
advantage), it would be nice if all the protocols were able to benefit
from the new code, not just http components.
Ok, ive said enough, flame on.
-Ryan
Stephen Colebourne wrote:
Oleg Kalnichevski wrote:
Can we expect any of the existing Commons [Net] committers to join the
project if we took the Commons [Net] on board? Would they be willing to
split the code base into a separate module per a network protocol?
Otherwise wouldn't it be kind of silly if we had almost a dozen modules
dedicated to various aspects of HTTP and one module containing all other
protocols (ftp, smtp, finger, and so on)?
My answer is 'I don't know'. As this is at the brainstorm level, I've
not yet proposed it to commons-net yet. (Think of it as offering you
guys first refusal).
I agree with your analysis though. To work sensibly, would involve
commons-net becoming smaller units.
Do you want me to propose the suggestion on commons-dev?
Stephen
---------------------------------------------------------------------
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]
