[Mono-devel-list] Patch against mod_mono to add certain features.
Daniel Lopez Ridruejo
daniel at rawbyte.com
Tue Apr 22 18:08:06 EDT 2003
On Tue, Apr 22, 2003 at 11:46:18PM +0200, yoros at wanadoo.es wrote:
> On Tue, Apr 22, 2003 at 02:46:32PM -0700, Daniel Lopez Ridruejo wrote:
> > I dont understand, why would you need a new MPM? It just needs to work with
> > a threaded MPM so all threads can share the same mono interpreter (or pool
> > of mono interpreters each one serving a different application, for example)
> I was reading on Apache2 modules and MPM is the only one that fits with
> our needs.
An MPM module is the one that defines the processing model: process based,
threaded, hybrid (multiple process each one which its own threads). That is,
how to create children processes or threads, accept connections and
distribute among the children.
The problem with a process based architecture (current one) is that each
child will have a separate instance of Mono so some things like session
support wont work because each one of the children will have a different
state. What mod_mono needs to do is work under a threaded based MPM. that
way it can create a Mono instance that can be shared by all worker threads.
This is the way taht mod_perl for Apache 2 is implemented (it also maintains
a pool of interpreters)
> For now, I'm still working on the remoting solution. I don't know why it
> doesn't work. I tried to use ApacheWorkerRequest as the remoted object,
> then I tried to use ApacheApplicationHost, it doesn't work... I will try
> to get the remoted layer between MonoWorkerRequest and System.Web.
More information about the Mono-devel-list