> So, I'm kind of curious what the general consensus is regarding this. Seems to be >in various directions.
I think JDBC should be a lot better; it should incorporate all the features of CrossDB (though maybe a little different), and some more. Then there should be higher-level tools like Torque that use it. Since JDBC has limitations, there should be something like a "patch" library that adds the extra features, while staying on the same level as JDBC. Torque should then use that. Whether the library should be a part of Torque or not is really only of marketing/exposure/etc concern; as long as its decoupled I'm happy. Jon indicates that this low level library already exists within Torque and that it is easy to use. If this is true, it may perhaps need some decoupling, and some of the stuff from CrossDB and similar OSS products fed into it. Since I will probably not do the programming of any of that anytime soon(no cycles), this is very IMHO. cheers, - Leo -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
