Is mod_ruby safe to use?


(Philip Mak) #1

Is it safe to use mod_ruby yet? I have to develop a small
database-driven website. I just discovered ruby this week and I like
the language. However, mod_ruby is listed in the RAA as being
"unstable". So I’m wondering if I should use mod_ruby, or stick with
what I know (mod_perl) for now.


(Sean Chittenden) #2

Is it safe to use mod_ruby yet?

Yes. I use mod_ruby extensively and have had no problems with it to
date. The classification of unstable will be changed when the module
goes 1.0, which should happen soon (best guess, less than a month). I
don't suspect a lot of code will be comitted between here and there
and would consider the current release VERY stable and production
worthy.

I have to develop a small database-driven website. I just discovered
ruby this week and I like the language. However, mod_ruby is listed
in the RAA as being "unstable". So I'm wondering if I should use
mod_ruby, or stick with what I know (mod_perl) for now.

Heh. I dropped mod_perl like a bad habbit and haven't looked back.
:~) -sc

···

--
Sean Chittenden


#3

I remember seeing not too long ago a little gotcha somewhere in the
mod_ruby documentation that you get memory leaks if you use ‘apachectl
restart’ because memory allocated by the interpreter wasn’t freed, but
I don’t see it now – was it fixed? That was the only issue that made
me hesitate to have it installed hither and yon.

–Jonathan

Sean Chittenden sean@chittenden.org wrote in message news:20020610122814.H71305@ninja1.internal

···

Is it safe to use mod_ruby yet?

Yes. I use mod_ruby extensively and have had no problems with it to
date. The classification of unstable will be changed when the module
goes 1.0, which should happen soon (best guess, less than a month). I
don’t suspect a lot of code will be comitted between here and there
and would consider the current release VERY stable and production
worthy.

I have to develop a small database-driven website. I just discovered
ruby this week and I like the language. However, mod_ruby is listed
in the RAA as being “unstable”. So I’m wondering if I should use
mod_ruby, or stick with what I know (mod_perl) for now.

Heh. I dropped mod_perl like a bad habbit and haven’t looked back.
:~) -sc


(Sean Chittenden) #4

I remember seeing not too long ago a little gotcha somewhere in the
mod_ruby documentation that you get memory leaks if you use
'apachectl restart' because memory allocated by the interpreter
wasn't freed, but I don't see it now -- was it fixed? That was the
only issue that made me hesitate to have it installed hither and
yon.

Actually, it's graceful that you have to watch out for, but that's not
a mod_ruby thing, it's an Apache DSO thing. Unless your handler
provides an explicity way of handling DSO reloads from the same PID,
Apache will just reload your DSO and will change the internal location
that it maps for the DSO (never freeing the old DSO). mod_perl
suffers from, as well as likely many other modules that are loaded via
DSO's. Moral of the story: use apachectl restart where possible.
'apachectl restart' actually brings the entire webserver down and
restarts it from scratch so you should be good to go no matter what.
-sc

···

--
Sean Chittenden