Am 25.03.2017 um 16:27 schrieb Massimo Manghi: > A single instance of the Apache HTTPD web server may be running > different web sites, still if they are based on different application > code it's safer to have separate interpreters. The current options are > therefore either one single interpreter or as many as the number of > virtual hosts. > > You may have a mixed situation where a number of web sites are running > the same application and the code might have been designed to properly > keep everything apart and at the same time other web sites following an > entirely different model. > > My proposal is to introduce a new configuration directive that creates > named rivet interpreter instances. This could be done having a directive > and changing the 3 available bridges accordingly, or we may exploit the > modular design of Rivet 3 to create a new threaded bridge capable of > handling named interpreters. The latter solution seems more enticing to > me, but demands the whole configuration code to introduce mpm bridge > specific directives > > I don't have time for setting out working on this but in case I will put > it on the TODO list for the summer
Sounds good. Thank you, Harald --------------------------------------------------------------------- To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org For additional commands, e-mail: rivet-dev-h...@tcl.apache.org
