On Wed, 1 Oct 2008, saurabh_engg2000 wrote: > Hi Guys, > > However, this alone cannot be the case.Rails Application run best in > the Mongrel.Hence you need a separate architechture for it > altogether.There are Gem packages required within the applications, > No one generally goes for shared hosting,for hosting their app, they > go for VPS or Slices or AWS, because only these allow the right kind > of hardware scaling(Multiple Mongels, and a load balancer like > nxginx),despite performing the normal scaling methods like Page > caching, fragment caching, memcached. >
Hi Saurabh: Thank you for the wonderful exposition on RoR. Please excuse me, if this sounds like a newbie query: Why Mongrel and not Apache webserver or ngineX for Rails apps ? i was just checking out Mongrel FAQ at http://mongrel.rubyforge.org/wiki/FAQ The FAQ says: As for the internals of Mongrel there are a few key technologies being used: * A custom HTTP 1.1 parser written based on the RFC standard and * using an ABNF dump thankfully put online by someone. The parser * is written using Ragel and is written C i& Java as Ruby extension. * A simple server that uses the parser and URIClassifier to process requests, find the right handlers, and then pass the results on to the handler for processing. * Handlers are responsible for using HttpRequest and HttpResponse objects to do their thing and then return results. Other than this there's not much more to it. Additionally, there is also a mod_rails (after mod_ruby) for Apache. Please see http://www.modrails.com/ What are your thoughts on Apache / modrails ? thanks Saifi.
