Am 29.07.2011 um 11:56 schrieb Mariano Martinez Peck:

On Fri, Jul 29, 2011 at 11:51 AM, Lukas Renggli <renggli@gmail.com> wrote:

>> Zinc can nicely play out the keep-alive. Kom doesn't support
>> keep-alive. With Swazoo a lot of requests fail if keep-alive is
>> enabled (so I disabled it). Details in the attachment.
>
> what is keep-alive?

The server keeps the socket open after a request-response cycle and
allows clients (browsers) to reuse the same socket for multiple
requests. This is typically faster than to open a new socket for each
request.

What is the difference between that and a database connection pool ?

Both are resource reusing techniques. But a database connection lies above a socket connection and is independent from it. You can send database request over an arbitrary socket connection to the database. This way you can't introduce a security problem. Pooling sockets is more difficult. If things communicating over the socket the authentication might going over that wire and authenticates the connection/socket instead of some abstracted session. In this scenario a socket pool would open a huge security problem giving access randomly to restricted sources.