Although we have customers on many different platforms (Linux, HP/UX, AIX, etc.), Java 5 has been available on these platforms for quite some time, and most of these customers have either already upgraded or will be doing so soon.
The issue of supporting old JVM¹s is tough. Corporate users often say they value reliability over new features, so it makes sense for them to be conservative. On the other hand, Java 6 is already out, and it seems unreasonable to constrain new FTP server development by compatibility with Java 1.4.2. Would it be acceptable to say that people who are tied to 1.4.2 must stick with older FTP server builds until they upgrade? We¹ve been stress testing with the code from November, and although we¹ve had to patch a couple of minor things, it has been quite solid. Clint On 1/1/07 8:52 AM, "Niklas Gustavsson" <[EMAIL PROTECTED]> wrote: > Hi all, > > for the planned integration with Apache MINA, we must make a choice on > what Java versions to support. MINA uses NIO for socket handling and NIO > only supports SSL from Java 1.5. MINA 1.0 therefore has a seperate > module for supporting SSL, while the remaining parts are compiled with 1.4. > > Moving to NIO and MINA will most certainly increase the scalability of > FtpServer significantly as we will no longer have one client, one thread > relationship. > > The way I understand it we have the following options: > > 1. Move all of FtpServer to require Java 1.5. > 2. Move out the SSL support into its own module, only support SSL with > Java 1.5, while regular FTP is supported from 1.4. > 3. Don't move to MINA, continue supporting 1.4. > > I'm clearly for option 1, I think that 1.5 has been out for long enough > and many other servers (like Tomcat and Geronimo) now requires 1.5. I > think option 2 would be unnecessarily complex for users to figure out. > > What do you think? I'm just starting with the MINA stuff and need to > know if anyone still needs 1.4 support. > > /niklas >
