Requiring NIO for H2 will most likely break compatibility with a whole bunch of embedded JVMs that either do not support NIO or have a broken/ unreliable/slow NIO implementation. If NIO is introduced it should be a configurable option so that one could still use a regular IO instead.
The same goes for requiring Java 1.5 classes like "java.util.concurrent". This will not play well with embedded JVMs where many are still at 1.4 API spec. My .02 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/h2-database?hl=en -~----------~----~----~----~------~----~------~--~---
