At 06:04 PM 11/5/2002 -0500, Rick Fincher wrote:

> >
> > Does Jaybird do JNDI?
>
>JNDI is more or less a resource locator. It can be used with any object.
>In this case with any JDBC driver. The driver is unaware of JNDI. The
>program uses JNDI to find out which driver to load, where it is on the disk
>(or the net), what the connection parameters are, etc.

Then I guess the question is: "does Jaybird publish JNDI
descriptions of itself, or must the user intuit the values
and create the descriptions?"

>Assuming that the SQL commands you use work with both.

Which is unlikely. No, Ann, don't start on standards. It
just gets you upset and antagonizes everyone else.

>Type 1 ...
>Type 4 talks directly to the database

OK. Understood.

>JayBird, a type 4 driver, makes calls directly to Firebird on port 3050,
>using whatever API Firebird expects. I presume this takes a lot more
>knowlege about the nitty-gritty of how the DB works.

Traditionally the wire protocol has been "private" meaning that
only the people who actually developed the client and server ends
needed to know what's in it. That allows for a great deal more
flexibility than a published API where every change must be upward
compatible etc. It also leads requiring that the client and server
be upgraded at the same time, which, to my way of thinking is a
bad thing.

>I'm not quite sure what you mean about checking remote protocol versions.

What I meant is precisely a handshake thing where the client says
"I speak protocols 2.1, 2.2, 3, 3.04, & 7". The server says "I
speak protocols 3.2, 4, 5, & 7". We agree on 7 and off we go.
However, in the past, the protocols have not been rigorously
labeled, so there are sometimes several variants that claim
be the same. What I'm advocating is strict adherence to protocol
versioning and possibly documenting the differences between
versions.

Skipping the java native red herring...

Regards,

Ann
www.ibphoenix.com