OK. Now I have a little time to get into this discussion. As I remember, we left off with a description of JDBC and ODBC and an open question as to which would be most appropriate for DRMAA, e.g. which best supports multiple sessions. To get this going, I'm just going to restate my previous assessment: the JDBC model is an object-oriented version of the ODBC model. Since we're working on a set of OO guidelines, I vote for the JDBC model. (Anyone surprised?) I would, however, love to hear arguments to the contrary. I don't want to force every binding to do things the Java way. I just want to do it the best wway. It's just that as it turns out, that *is* the Java way... :) Daniel