| Subject | Re: [IB-Java] Re: Dying connections with interclient |
|---|---|
| Author | Jim Starkey |
| Post date | 2001-04-17T20:46:51Z |
At 10:33 PM 4/17/01 +0200, you wrote:
local Interbase API which may connect to a local engine or to a
server somewhere else on the network.
In the Interbase architect, you never talk directly to an engine
but to a prosaically named Y-valve (piece of nautical gear) that
to a local engine, a remote server, and in the good old days,
a gateway to a different vendor's dbms or a previous version of
an Interbase engine. But ya gotta start somewhere, and that
somewhere is gds32.dll.
Jim Starkey
>No, that's not what that means. Interserver needs to talk to the
> No, I am not sure about anything. Right now I installed InterServer on
> a clean w2k machine and tried to run it. It did not start:
>
>""
> to have Interbase installed on the
> same
> box.
> Please, tell me, how I can install the 2 boxes system: 1 machine listen
> almost everything (httpd:80,jsp:8080,interserver:3060,rmiregistry:1099) and
> another one has only Interbase:3050 and database itself
>
local Interbase API which may connect to a local engine or to a
server somewhere else on the network.
In the Interbase architect, you never talk directly to an engine
but to a prosaically named Y-valve (piece of nautical gear) that
to a local engine, a remote server, and in the good old days,
a gateway to a different vendor's dbms or a previous version of
an Interbase engine. But ya gotta start somewhere, and that
somewhere is gds32.dll.
Jim Starkey