[Mono-list] ASP.NET - usability/robustness/safety
Fri, 23 Jul 2004 10:52:39 -0600
In answer to your question #2, I run a site that we launched a couple
of weeks ago (www.edcomp.com) using asp.net and mono. Right now it is
getting 2000 visitors a day and 5000 page views. So it's not a hobby
site but not a full commercial site either.
So far there have been some problems, but nothing that I would
consider too severe. I have run into problems where it appears that
the mod_mono_server is not releasing memory properly if left to run
too long. I end up having to shut down mod_mono_server once a week to
prevent it from crashing apache. I'm not sure why this is happening.
The other inconvenience is that I use code-behind. Right now
mod_mono_server does not recognize changes to the assembly and won't
load the new assembly unless you kill and restart the server. I have
heard that there is a patch that makes it so you only need to restart
apache to get the changes, but I haven't installed it yet.
I have been using mono for asp.net for about 5 months now and have
been really impressed. I prefer using asp.net on a Windows machine,
but where I am limited to using Linux it works great.
On Fri, 23 Jul 2004 09:18:02 -0700 (PDT), Ron Afloh <email@example.com> wrote:
> I had a few questions about ASP.NET as supported by
> mono and apache. In short, i'm considering using it
> to write a commercial webpage and wanted to get
> feedback from you guys on how good/bad of an idea this
> 1) Is the ASP.NET mono sections + apache plugin "ready
> for primetime" -- i.e., has this stuff been "load"
> tested, is the security there, can it scale to handle
> a fairly large website?
> 2) Are any other non-hobby sites using mono's asp.net
> 3) If the asp.net stuff is not ready for full blown
> commercial websites.... any ideas on when that level
> of robustness/security/load-handling will be there?
> 4) From what i've read, ASP.NET is not covered under
> ECMA specs and therefore is not as legally safe from
> lawsuit from MS as the compiler/JIT/corelibs are. So
> would it be stupid to risk using mono's ASP.NET
> implementation for a commercial venture -- i.e., too
> risky legally?
> I did read the FAQ and searched the last few months of
> postings and didn't really see anything that answered
> all of these -- hopefully i didn't miss anything to
> obvious :) I'm also aware that some of these
> questions are not black and white and may not have an
> answer at all -- regardless, i appreciate everyones
> input and suggestions.
> Cheers -
> Do you Yahoo!?
> Vote for the stars of Yahoo!'s next ad campaign!
> Mono-list maillist - Monofirstname.lastname@example.org