[Mono-dev] FastCGI, was: Silverlight early implementation thoughts.

[Robert Jordan]

Hey Marek,

Marek Habersack wrote:
> 
> This is still much easier to cope with than mod_mono abrakadabra, IMHO :)
> Even if some people will consider it to be harder, the configuration above is
> specific to apache only and with FastCGI we will be able to use any other
> webserver that supports the protocol. This is, in my eyes, the biggest
> advantage of having such bridge (in addition to using a standard,
> well-supported protocol to handle the requests).

W/out any doubt, fastcgi has a lot of advantages. I don't want to
criticize it. Just its configuration could be a problem for apache
newbies, but ...

>> Configuring an application-to-mono-process mapping, easily
>> to achieve with mod_mono, will become a nightmare with FastCGI.
>> Moreover, the config snippets above must be inserted in
>> every vhost, otherwise the vhosts will share the same
>> mono-fastcgi-server process.
> That's not entirely true. Please read
> 
> http://www.fastcgi.com/mod_fastcgi/docs/mod_fastcgi.html#FastCgiWrapper
> 
> With the help of the above you can create a dynamic setup that suits your needs.

... if Mono will provide its own configuration manager using a
wrapper (which hopefully won't badly interfere with other fastcgi apps
(e.g. php) on the same server), I'm fine with it :-)

Are there any plans to make the wrapper interactive (a web
app of its own), like a small application server?

Robert