Hum, it would be infinitely more convenient, for deployment purposes, not to
touch the driver at all. What I can do maybe is to hack the driver with
reflection, since private fields can be accessed as well (except in applets).
Since you've done it before, would you mind sharing the caveats you went
through, general warnings and also the particular class where the receiving
InputStream for the ResultSet is? That would save a lot of time!
Also, the ability to monitor the amount of bytes loaded would be an nice
addition to the driver itself. Perhaps a small Monitor class that extends
Thread, which monitors the receiving InputStream and provides a single
getLoadedBytes() method?
Thanks for your insight Nicholas.
Albert