| Subject | Re: [ib-support] Re: Help with Multi-threaded application on Localhost |
|---|---|
| Author | Helen Borrie |
| Post date | 2003-02-25T13:30:15Z |
At 12:58 PM 25/02/2003 +0000, you wrote:
connection under SuperServer isn't designed for multi-threaded connections.
You need to use the local loopback connection, so that the network layer is
used for client-server communication, in a manner that emulates a remote
TCP/IP connection.
Naturally, running local client threads won't ever be as efficient as
remote client connections, since each individual thread is going to steal
machine resources from the server...but you get what you pay for in
computer land.
Have you considered moving your server onto a Linux server box on its own,
and running your comparatively resource-hungry application tier as a remote
fat client? This way, machine capacity limitations won't get into the
equation, it's cheap and it's highly scalable.
heLen
> > does the server application (thread) connect withIt's wrong for what you are doing. Why? because the local server
> >
> > localhost:D:\path_to_db\MyDB.gdb
> >
> > or
> >
> > D:\path_to_db\MyDB.gdb
>Sorry ! I set Database parameter in "Connection" object to something
>like d:\databases\MyDB.gdb. Is that wrong and why?
connection under SuperServer isn't designed for multi-threaded connections.
You need to use the local loopback connection, so that the network layer is
used for client-server communication, in a manner that emulates a remote
TCP/IP connection.
Naturally, running local client threads won't ever be as efficient as
remote client connections, since each individual thread is going to steal
machine resources from the server...but you get what you pay for in
computer land.
Have you considered moving your server onto a Linux server box on its own,
and running your comparatively resource-hungry application tier as a remote
fat client? This way, machine capacity limitations won't get into the
equation, it's cheap and it's highly scalable.
heLen