> Since we're talking about splitting off of 1.x and all this
> refactoring, we probably ought to agree on a minimum VM level.
> Discussion of NIO implies at least JDK 1.4.
> Personally, I have not problem with that. But it's probably
> worthwhile making sure a majority of the users are ready to give
> up support on JDK 1.3...
Right, that is obviously an important point.
Our company and products always need to work with the latest stuff, so
1.4 is mandatory for us.
If the NIO API's turn out to be as useful as they seem, it should be a
Another thing I'm also doing in my own refactoring is adding better
support for logging, through monitors. In other words, instead of doing
log messages in the code it calls monitors, one popular implementation
of which would be to create a log message. This opens up for more
customized monitoring of the database, and doesn't pollute the core code
with this or that logging package.