| Subject | Re: [ib-support] Spec for direct connection to firebird through TCP/IP |
|---|---|
| Author | pschmidt@interlog.com |
| Post date | 2002-10-11T12:27:32Z |
On 11 Oct 2002 at 0:23, Christoph wrote:
need to use the wire protocol, which is the internal way that the server and client
talk to each other. The problem is that the wire-protocol is engine version specific,
there is no guarantee that the wire protocol for Firebird 1.5 will in any way resemble
the wire protocol for Firebird 1.0 (it probably will, but there are no guarantees).
The ODBC drivers use gds32, JBird doesn't because it's a pure Java driver, but the
JBird team and the engine team need to stay in communication so that any changes
in the wire protocol get sent to the JBird team so that they can update the driver.
This applies to just about every database out there, not just Interbase.
>That fits in the category of a really, really bad idea, to get around gds32 you would
> Is there a spec for how to connect, run sql and get results by
> directly connecting to the database using TCP/IP?
>
> I know that I could probably look at the ODBC or JDBC driver source
> but I was wondering if there is something more formal out there?
>
> I would like to avoid using gds32 if possible.
>
need to use the wire protocol, which is the internal way that the server and client
talk to each other. The problem is that the wire-protocol is engine version specific,
there is no guarantee that the wire protocol for Firebird 1.5 will in any way resemble
the wire protocol for Firebird 1.0 (it probably will, but there are no guarantees).
The ODBC drivers use gds32, JBird doesn't because it's a pure Java driver, but the
JBird team and the engine team need to stay in communication so that any changes
in the wire protocol get sent to the JBird team so that they can update the driver.
This applies to just about every database out there, not just Interbase.