| Subject | RE: [IB-Java] Re: Dying connections with interclient |
|---|---|
| Author | Goedhart, Andrew |
| Post date | 2001-04-18T07:47:50Z |
Does this mean that there is a JDBC driver available that doesn't use
Interserver that can act as a starting point for a Firebird open source
implementation of java interbase connectivity. Or am I just being hopefull
:-)
If this is the case where can I get hold of it and a description of the port
3050 protocol so that things can begin.
Andrew
-----Original Message-----
From: Jim Starkey [mailto:jas@...]
Sent: 17 April 2001 22:40
To: IB-Java@yahoogroups.com
Subject: RE: [IB-Java] Re: Dying connections with interclient
At 04:21 PM 4/17/01 -0400, you wrote:
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
To unsubscribe from this group, send an email to:
IB-Java-unsubscribe@egroups.com
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Interserver that can act as a starting point for a Firebird open source
implementation of java interbase connectivity. Or am I just being hopefull
:-)
If this is the case where can I get hold of it and a description of the port
3050 protocol so that things can begin.
Andrew
-----Original Message-----
From: Jim Starkey [mailto:jas@...]
Sent: 17 April 2001 22:40
To: IB-Java@yahoogroups.com
Subject: RE: [IB-Java] Re: Dying connections with interclient
At 04:21 PM 4/17/01 -0400, you wrote:
> I thought you would have written theEctually, it was a Netfrastructure customer who wanted to
> jni wrappers for that old odbc code you had around by now.
>
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
To unsubscribe from this group, send an email to:
IB-Java-unsubscribe@egroups.com
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/