You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Rory Winston <rw...@eircom.net> on 2006/01/28 21:36:15 UTC
[net] JDK 1.4+ Branch?
Hi
I have been following the email threads re: JSSE and FTPS functionality.
I think that this might be a good point to consider introducing a
version of Commons-Net that uses JDK 1.4+ as a baseline. My reasoning is
as follows:
* We could remove the (oro) jar dependency;
* FTPS support would not necessitate a separate (JSSE) jar dependency;
* It could be a good opportunity to "clean up" the threading code and
socket handling, and make use of NIO;
* It also may be easier to incrementally add new functionality, such as
Proxy support
Of course, JDK-1.3-compatible releases could still continue on HEAD, or
we could move the 1.4+ branch to HEAD and the 1.3 code to a maintenance
branch.
As a simple proof-of-concept, I have set up a sandbox branch and made
some minor enhancements, including:
* Changing oro-dependant code to use Java regex code instead
Any comments?
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [net] JDK 1.4+ Branch?
Posted by Steve Cohen <sc...@javactivity.org>.
Right. That is the question we have to answer.
I guess I'm okay with it but I'm not quite a +1 yet until I understand
how much work is involved. I notice a couple of the Jakarta Commons
projects do separate branches:
Collections and HttpClient. There may be others, these were just the
ones visible at 1 click from the Downloads page.
It would certainly help us solve the FTPS issue.
Rory Winston wrote:
> Steve
>
> Agreed that JDK 1.3 (and previous) is still important to support. My
> question is: is it desirable to put a 1.4+ version on HEAD and relegate
> JDK 1.3 to a separate branch, or do we not want to get into separate
> branch maintenance?
>
> R
>
> Steve Cohen wrote:
>
>> Rory Winston wrote:
>>
>>> Hi
>>>
>>> I have been following the email threads re: JSSE and FTPS
>>> functionality. I think that this might be a good point to consider
>>> introducing a version of Commons-Net that uses JDK 1.4+ as a
>>> baseline. My reasoning is as follows:
>>>
>>> * We could remove the (oro) jar dependency;
>>> * FTPS support would not necessitate a separate (JSSE) jar dependency;
>>> * It could be a good opportunity to "clean up" the threading code and
>>> socket handling, and make use of NIO;
>>> * It also may be easier to incrementally add new functionality, such
>>> as Proxy support
>>>
>>> Of course, JDK-1.3-compatible releases could still continue on HEAD,
>>> or we could move the 1.4+ branch to HEAD and the 1.3 code to a
>>> maintenance branch.
>>>
>>> As a simple proof-of-concept, I have set up a sandbox branch and made
>>> some minor enhancements, including:
>>>
>>> * Changing oro-dependant code to use Java regex code instead
>>>
>>> Any comments?
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>>
>>>
>>>
>> The only negative I can find is that our contributor of the FTPS stuff
>> badly wants 1.3 compatibility. And I have a feeling that he's not the
>> only one. 1.3 is not yet End of Life according to Sun, although it
>> will be soon. My sense is that we lag Sun by some interval of time on
>> these issues. I don't think we're going to be able to get away with
>> saying "no more enhancements for JDK1.3" for awhile. So this will
>> probably mean maintaining two branches for some time.
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [net] JDK 1.4+ Branch?
Posted by Rory Winston <rw...@eircom.net>.
Steve
Agreed that JDK 1.3 (and previous) is still important to support. My
question is: is it desirable to put a 1.4+ version on HEAD and relegate
JDK 1.3 to a separate branch, or do we not want to get into separate
branch maintenance?
R
Steve Cohen wrote:
> Rory Winston wrote:
>
>> Hi
>>
>> I have been following the email threads re: JSSE and FTPS
>> functionality. I think that this might be a good point to consider
>> introducing a version of Commons-Net that uses JDK 1.4+ as a
>> baseline. My reasoning is as follows:
>>
>> * We could remove the (oro) jar dependency;
>> * FTPS support would not necessitate a separate (JSSE) jar dependency;
>> * It could be a good opportunity to "clean up" the threading code and
>> socket handling, and make use of NIO;
>> * It also may be easier to incrementally add new functionality, such
>> as Proxy support
>>
>> Of course, JDK-1.3-compatible releases could still continue on HEAD,
>> or we could move the 1.4+ branch to HEAD and the 1.3 code to a
>> maintenance branch.
>>
>> As a simple proof-of-concept, I have set up a sandbox branch and made
>> some minor enhancements, including:
>>
>> * Changing oro-dependant code to use Java regex code instead
>>
>> Any comments?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>
>>
>>
> The only negative I can find is that our contributor of the FTPS stuff
> badly wants 1.3 compatibility. And I have a feeling that he's not the
> only one. 1.3 is not yet End of Life according to Sun, although it
> will be soon. My sense is that we lag Sun by some interval of time on
> these issues. I don't think we're going to be able to get away with
> saying "no more enhancements for JDK1.3" for awhile. So this will
> probably mean maintaining two branches for some time.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [net] JDK 1.4+ Branch?
Posted by Steve Cohen <sc...@javactivity.org>.
Rory Winston wrote:
> Hi
>
> I have been following the email threads re: JSSE and FTPS functionality.
> I think that this might be a good point to consider introducing a
> version of Commons-Net that uses JDK 1.4+ as a baseline. My reasoning is
> as follows:
>
> * We could remove the (oro) jar dependency;
> * FTPS support would not necessitate a separate (JSSE) jar dependency;
> * It could be a good opportunity to "clean up" the threading code and
> socket handling, and make use of NIO;
> * It also may be easier to incrementally add new functionality, such as
> Proxy support
>
> Of course, JDK-1.3-compatible releases could still continue on HEAD, or
> we could move the 1.4+ branch to HEAD and the 1.3 code to a maintenance
> branch.
>
> As a simple proof-of-concept, I have set up a sandbox branch and made
> some minor enhancements, including:
>
> * Changing oro-dependant code to use Java regex code instead
>
> Any comments?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
>
The only negative I can find is that our contributor of the FTPS stuff
badly wants 1.3 compatibility. And I have a feeling that he's not the
only one. 1.3 is not yet End of Life according to Sun, although it will
be soon. My sense is that we lag Sun by some interval of time on these
issues. I don't think we're going to be able to get away with saying
"no more enhancements for JDK1.3" for awhile. So this will probably
mean maintaining two branches for some time.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org