No True "mod_ruby" Is Damaging Ruby's Viability On The Web
Popularity Report
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
Bookmark History
Public Sticky notes
he reason is that applications built around these frameworks tend to expose themselves directly via HTTP daemons, using libraries such as Mongrel or WEBrick, and then requests from Web servers like Apache need to be proxied through to them, but this feels like a hackish workaround to the fact we lack a proper "mod_ruby."
Highlighted by harryli


Public Comment
on 2008-01-18 by ratbeard