At 04:21 PM 4/17/01 -0400, you wrote:

> I thought you would have written the
> jni wrappers for that old odbc code you had around by now.
>

Ectually, it was a Netfrastructure customer who wanted to
use interserver. And a customer with a live checkbook
is a fine customer indeed.

Going the other direction (jdbc -> netfrastructure) I had
a change in strategy following some pontification on the
IB-architecture list. I had originally planned to layer
my JDBC driver on my remote interface (polymorphic twin
to the ISCDBC portion of the IBPhoenix ODBC driver). But
after my sage advice about a Firebird JDBC implementation
talking directly to 3050, I took my own advice, and converted
by JDBC driver to talk line protocol to the Netfrastructure
server. Turned out to take the better part of a Sunday
afternoon to get the whole thing basically functional.
So now I have a super thin, 100% pure Java jdbc driver without
either "native" code or a ridiculous intermediate server.

The very (only?) nice thing about being a small underfinanced
company is that you can't afford to do things stupidly.
Make something like a JDBC driver somebody's full time job
and you get a massively complex [unkind term omitted] like
interclient/interserver. Tell yourself that you can't do
anything fun until you both eat your vegetables and write
a JDBC driver, you get quite a different architecture.

Jim Starkey