On this same note, we've been talking about the two architectures here, and
the direction of FB 3:
It's my understanding that with FB-Classic, when you make a new connection to
the server (either from a new process or a new thread), you get a new TCP
socket, which effectively gives you scalable IPC bandwidth. Instead of trying
to ram all connections through one socket, you spread them out over multiple
sockets, and this might be a big advantage on a multi-core system.
I read somewhere that the FB 3 architecture is leaning towards SuperServer. I
don't know if SS multiplexes all connections over a single socket today, but
if so, we'd like to put in our two cents worth here and say that we think
that multiple IPC pipes to the back-end server are probably a good thing.
- Bud
Bud Millwood
Weird Solutions, Inc.
http://www.weird-solutions.comtel: +46 8 758 3700
fax: +46 8 758 3687
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaoneFirebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
