> On Feb 4, 2018, at 5:49 AM, Stefan Eissing <stefan.eiss...@greenbytes.de> > wrote: > > > Initially, ServerUID sounded like a tweak, but now we are talking > about the identity of a server_rec across reloads and how that > can be useful. >
But does it need to be a user Directive? I still say it is not needed whether or not. My point is that each module is free to determine what makes a Vhost "unique", all by itself, across graceful restarts, across restarts with config file changes, etc... It is all based on the assumption that, TO THAT MODULE, what "is" a unique Vhost. And that assumption is not absolute. It depends on the use case. And modules, via post_config and determining which post config # it is, can create it's own internal ServerUID for whatever it needs to use it for. There is no need for this to be some external ID for the user land. So even if we create this directive, we will undoubtedly run into cases where people say "Well, it doesn't do exactly what I want.... I want ServerUID to change when I do 'foo' or remain the same when I do 'bar'" and we will add additional fluff and cruft. It's a solution looking for a problem.
