At 03:30 PM 4/18/01 -0400, you wrote:

> Hi,
> I may be all wrong about this, if so please let me know.
>
> My impression is that gds.so is the c client library and that it is what
> It is intended to be linked into your
> Interserver exists because Borland didn't want to replace
> gds.so with java code that talks to port 3050, but they did want to have a
> So they wrote a C program that talks to java on one end

Any assumption that intelligence, knowledge, or insight entered into
the Borland decision making process is all wet. The decision was
almost certainly made by a relative junior guy who wanted to get as
much distance between himself and the Borland "management" as possible
(I understand he finally decided that a thousand miles and the Rocky
Mountains was enough; he may have since reconsidered).

> The two ways to
> eliminate the extra layer are:
>
> 1. Give up on pure java, write jni code that talks locally to gds.so
>
> 2. Rewrite the functionality of gds.so in java so we get a pure java
> driver.
>
> Jim was originally proposing (1) using his c++ odbc driver, but as I
> understand it has decided (2) is a better solution, and apparently easy to
> I hope it's just as easy for firebird!
>

I'm sorry if I mislead anyone on this personal bit of bravado.
Netfrastructure was written to JDBC specifications so no translation
was necessary. Depending on your point of view I either a) cheated
or b) acted with clear prescient insight...



Jim Starkey