> This is how it works right now. But how many concurrent transactions
> can you support? If you have a lot of databases and many clients that
> start/suspend/resume/end their transactions, and most of the
> transactions are suspended, then you will simply run out of sockets.
> 20 databases with 50 running transactions (event read-only) in each
> database means 1000 open sockets.

But isn't Firebird able to have several transactions for one connection ?
Wouldn't that solve that specific problem ?


Berenger