[Mono-bugs] [Bug 71867][Wis] Changed - Multiple MonoApplications Directives

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Sun, 6 Feb 2005 17:19:07 -0500 (EST)

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 gonzalo@ximian.com.


--- shadow/71867	2005-01-28 13:01:36.000000000 -0500
+++ shadow/71867.tmp.2264	2005-02-06 17:19:07.000000000 -0500
@@ -39,6 +39,33 @@
 Have you tried moving the MonoApplications into <Location>?
 ------- Additional Comments From rlyon@novell.com  2005-01-28 13:01 -------
 If I move "MonoApplications" into the Location tag, I get:
 MonoApplications not allowed here
+------- Additional Comments From gonzalo@ximian.com  2005-02-06 17:19 -------
+There's a problem here... Those Mono* options you set in the apache
+config file are passed as arguments to mod-mono-server... And we only
+run 1 mod-mono-server.
+mod-mono-server is now being launched when apache starts, so the
+options outside Location/Directory are used for it. If I enable
+including, for example, a different MonoApplications inside
+Location/Directory and you set a different MonoApplications in there,
+it will not be used by the already running mod-mono-server.
+A different case would happen if you wanted mod-mono to start/connect
+ to different mod-mono-server processes, which i think it's not the case.
+So, even if you're running different asp.net applications, there can
+only be a single MonoApplications. For the case above:
+MonoApplications "/demo1:/opt/demo1,/demo2:/opt/demo2"
+As an alternative, assuming we do not want more than one
+mod-mono-server.exe, I could have a AddMonoApplication directive so
+that you can have it in different files (still outside
+Let me know what you think.