Bernd:
Database clients can keep a connection open and send multiple requests. This
is commonly done in TCP/IP based, non-HTTP, proprietary protocols. If they
want to optimize, they write server side procedures and invoke them in one
request.
I can limit the workers to 1. This will “solve”
Hello,
It is generally not a good idea to keep a database transaction open over
multiple requests, if you need that you would need to bind the connection
object to the session (which is I guess not easily possible in CGI or native
code).
Those kinds of session questions are best asked in the
Bernd:
I have a use case in which the client wants to perform a transaction that uses
a database connection. The database connection is associated with a worker.
The client has the URI to the database connection but the client’s GET/POST
etc. have to be routed to the correct worker/child.
The Apache HttpComponents project is pleased to announce 4.1.4 GA
release of HttpComponents HttpAsyncClient.
This is a maintenance release that adds Automatic-Module-Name to the
manifest for compatibility with Java 9 Platform Module System and fixes
a number of issues discovered since 4.1.3
Hello,
I am pretty sure there is no way to connect to a specific listener. However I
am also pretty sure you would have to ask Httpd or Nginx projects instead.
However I am also sure that you normally don’t need it, must of the caches are
shared across all the workers (or sessions beeing
