Hi,

Using classic you'll have 1 fb_inet_server for each client connection (not
for each statemant) plus 1 (the 'listener' service)

I've been using Classic over Windows 2003 on about 3 sites for some time
now. In my experience it's a *lot* better/faster than SS if you're running
on a SMP box. And memory is not an issue, you'll usually need more then with
SS but not that much.

The only "bad" is that it *seems* each instance does not kill itself when
the client have lost connection (eg. crashed), even after some big time. And
I'm not sure database shutdown works fine too.

But, usually u can live with it ;-)

----- Original Message -----
From: "mohamed.banaouas"


Our application (client-side) maintain opened the firebird connection
during all the user session, so I think there is no need to lunch
fbserver copy any moore ? Unless the lunch concerns each query...
I asked the question about windows/classic because I did't notices
many threads about it. I'm really interested on feedback about such
association.

thanks in advance