[Info-vax] New OpenSSL update from HP

[David Froble]

JF Mezei wrote:
> Here is the Apache config (/etc/apache2/httpd.conf) with reg server
> process pool :
> 
> ## Server-pool size regulation.  Rather than making you guess how many
> ## server processes you need, Apache dynamically adapts to the load it
> ## sees --- that is, it tries to maintain enough server processes to
> ## handle the current load, plus a few spare servers to handle transient
> ## load spikes (e.g., multiple simultaneous requests from a single
> ## Netscape browser).
> ##
> ## It does this by periodically checking how many servers are waiting
> ## for a request.  If there are fewer than MinSpareServers, it creates
> ## a new spare.  If there are more than MaxSpareServers, some of the
> ## spares die off.  The default values are probably OK for most sites.
> ##
> MinSpareServers 8
> MaxSpareServers 64
> ##
> ## Number of servers to start initially --- should be a reasonable ballpark
> ## figure.
> ##
> StartServers 1
> 
> 
> 
> The one area where Apache may use facilities for which VMS is not well
> designed is the master process handing an incoming TCP request to a
> different process. I recall some discussions about that on c.o.v. a few
> years back.

Yeah, and it's still not documented ....

When I talked with Mark about this, I seem to recall that he indicated 
that in WASD the worker process never read from the socket, just wrote 
to it.

My preference would be to have the listener grant the connection, and 
then hand the socket off to a worker process for all communications.

Steve thinks I should use the Aux Process capability in TCP/IP.  I'd 
rather create my own processes.

And it's still not documented, that I've been able to find ....