Hi. I'm interested in having a DRDA server that invokes other databases besides embedded-Derby. Perusing the Derby drda server-side code, it appears to be somewhat bound to Derby. So I was thinking that one approach would be to create a DRDA API that is not tied to Derby (or any particular database), then refactor the Derby classes (from package org.apache.derby.impl.drda) to cleanly separate the Derby-specifics from the DRDA parsing.
So, I'm wondering what anyone thinks about this idea - how feasible, is it worth bothering with, any other suggestions? Thanks, Lee
