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

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Mon, 7 Feb 2005 14:02:16 -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-02-07 12:59:32.000000000 -0500
+++ shadow/71867.tmp.20130	2005-02-07 14:02:16.000000000 -0500
@@ -1,12 +1,12 @@
 Bug#: 71867
 Product: Mono: Tools
 Version: 1.1
 OS: unknown
 OS Details: 
-Status: NEW   
+Status: ASSIGNED   
 Severity: Unknown
 Priority: Wishlist
 Component: mod_mono
 AssignedTo: gonzalo@ximian.com                            
 ReportedBy: rlyon@novell.com               
@@ -96,6 +96,22 @@
 an iterative value, but I can work with a new tag.
 In the future, I can see the need for multiple mod-mono-servers.  
 What are your plans for the future of mod_mono?
+------- Additional Comments From gonzalo@ximian.com  2005-02-07 14:02 -------
+Okay. I'll add AddMonoApplication(s) directive to be used outside
+About supporting more than one mod-mono-server...
+If they are not started by mod_mono, it would be a matter of allowing
+MonoUnixSocket/MonoListen* inside Location/Directory. This is easy to
+If they are to be started by mod_mono we would need some thinking on
+how to tell the module about that with directives out of
+Directory/Location, as we want to run mod-mono-server during the
+child_init stage.