[Mono-bugs] [Bug 50049][Maj] Changed - MonoThread domain-specific handling broken

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by deobalds@uregina.ca.

http://bugzilla.ximian.com/show_bug.cgi?id=50049

--- shadow/50049	2004-10-22 00:30:17.000000000 -0400
+++ shadow/50049.tmp.5443	2004-11-10 03:37:36.000000000 -0500
@@ -127,6 +127,32 @@
 
 ------- Additional Comments From vargaz@gmail.com  2004-10-18 20:25 -------
 Lets try fixing this bad guy.
 
 ------- Additional Comments From vargaz@gmail.com  2004-10-22 00:30 -------
 *** Bug 68323 has been marked as a duplicate of this bug. ***
+
+------- Additional Comments From deobalds@uregina.ca  2004-11-10 03:37 -------
+This bug has a workaround which works quite well. Seperate versions of
+mod-mono-server.exe can be run by setting the `MonoUnixSocket' and
+`MonoWapiDir' directives for each individual VirtualHost directive,
+like so:
+
+MonoApplicationsConfigDir "/etc/httpd/conf/monoapps"
+MonoUnixSocket "/tmp/VirtualHosts/sitename/mono_socket/monosock"
+MonoWapiDir "/tmp/VirtualHosts/sitename/wapi"
+
+Note 1: As you can see above, you also have to set
+`MonoApplicationsConfigDir' (or an equivalent, such as
+`MonoApplicationsConfigFile') for each VirtualHost directive - I'm not
+sure if this is a bug itself or not, since I would intuitively think a
+global `MonoApplicationsConfigDir' would work.
+
+Note 2: For anyone reading this and wondering how to set up
+`/tmp/VirtualHosts/*', Joseph Hill (gotmono.net's ASP.net guru)
+suggested running a small script on apache start which creates the
+`/tmp/VirtualHosts/sitename/mono_socket' and
+`/tmp/VirtualHosts/sitename/wapi' directories. (The `monosock' file
+will be created automatically.) Then just do an `rm -rf
+/tmp/VirtualHosts' on apache stop, and you should be all set. If
+anyone has a better way of doing this, Joseph and I are always
+interested. :)