On Mon, Jul 11, 2016 at 5:25 AM, Stefan Eissing < stefan.eiss...@greenbytes.de> wrote:
> In https://bz.apache.org/bugzilla/show_bug.cgi?id=59840 the issue crept > up that StdEnvVars makes concurrent access to the SSL context when HTTP/2 > is in place. > > The question is: how do we want to fix this? > > The general theme is that a module needs to perform some action on a > connection, sees that it is a slave connection and accesses the master > instead. Such a module needs to be aware that access to master may happen > in parallel with other request. > > Should we let each such module care for it on its own or do we want to > provide a way to access the master connection in a mutex protected way? > Rather than a mutex, which would become an issue because all master access to the context would require blocking, is there a way we can allow a module to perform its (hopefully swift) processing on the master thread? Send a metadata bucket to the master asking for a function to be invoked?
