I think anyone who has a need to support over 200 concurrent connections
should look into using a multi-tier architecture for their application. This
makes it such that multiple computers can pool up 5-10 connections each
across a high-speed LAN to a high-end machine hosting the database. Thus,
each middle tier machine can probably host up to about 100-200 clients
actively working with the database. Products like ASTA and MIDAS are good
examples but I believe that other ISAPI or JAVA apps would perform a similar
function as well. In this way you would be able to load balance the burden
of so many active clients across an array of machines and funnel their work
to the database through pooled connections, no more that 50-100 of them.
This should fit quite well within the connection limitations of the
platforms InterBase runs on.

FWIW,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com

----- Original Message -----
From: "Andre Mostert" <amostert@...>
To: <IB-Architect@egroups.com>
Sent: Wednesday, July 05, 2000 2:48 PM
Subject: Re: [IB-Architect] Interbase connection limit and Support
relatedProblems


> We encountered a similar problem on NT. Charlie Caro post a message to
list
> a week ago confirming it was the same problem. NT seems to accept the
> connections above 256, ie the client apps do not get an error, but neither
> do the get any response from the server.
>
> Regards Andre
>
> -----Original Message-----
> From: Jason Chapman <jason@...>
> To: IB-Architect@egroups.com <IB-Architect@egroups.com>
> Date: Wednesday, July 05, 2000 10:43 PM
> Subject: Re: [IB-Architect] Interbase connection limit and Support
> relatedProblems
>
>
> What about NT?
>
> My largest customer has just blown 256!
>
> JAC.