Comments on: HOWTO: Custom Mongrel Handlers http://adam.blogs.bitscribe.net/2007/05/06/howto-custom-mongrel-handlers/ software sophistry Thu, 28 Aug 2008 02:14:04 +0000 http://wordpress.org/?v=2.3.2 By: reality » Blog Archive » Ruby on Rails + AJAX + Mongrel + JMS/MQ/MOM = 即時通訊 http://adam.blogs.bitscribe.net/2007/05/06/howto-custom-mongrel-handlers/#comment-12472 reality » Blog Archive » Ruby on Rails + AJAX + Mongrel + JMS/MQ/MOM = 即時通訊 Sun, 01 Jul 2007 18:00:52 +0000 http://adam.blogs.bitscribe.net/2007/05/06/howto-custom-mongrel-handlers/#comment-12472 [...] HOWTO: Custom Mongrel Handler - Building mongrel http handler [...] […] HOWTO: Custom Mongrel Handler - Building mongrel http handler […]

]]> By: adam http://adam.blogs.bitscribe.net/2007/05/06/howto-custom-mongrel-handlers/#comment-6437 adam Fri, 11 May 2007 11:07:26 +0000 http://adam.blogs.bitscribe.net/2007/05/06/howto-custom-mongrel-handlers/#comment-6437 Pratik - As Rick pointed out, you actually do have most of the Rails environment. Mongrel is running in the same VM process as Rails. What you don't get is ActionController, which includes stuff like automatic parsing of your CGI parameters, sessions, and template rendering. (It should be possible to render ERB with lower-level calls, although ERB is pretty slow too, so if you're doing this for optimization's sake that might be counterproductive.) Pratik -

As Rick pointed out, you actually do have most of the Rails environment. Mongrel is running in the same VM process as Rails. What you don’t get is ActionController, which includes stuff like automatic parsing of your CGI parameters, sessions, and template rendering. (It should be possible to render ERB with lower-level calls, although ERB is pretty slow too, so if you’re doing this for optimization’s sake that might be counterproductive.)

]]> By: Pratik http://adam.blogs.bitscribe.net/2007/05/06/howto-custom-mongrel-handlers/#comment-6436 Pratik Fri, 11 May 2007 10:28:52 +0000 http://adam.blogs.bitscribe.net/2007/05/06/howto-custom-mongrel-handlers/#comment-6436 I'm wondering if it's possible to subclass the handler from Mongrel::Rails::RailsHandler instead of Mongrel::HttpHandler and get the entire rails environment inside the handler ? I’m wondering if it’s possible to subclass the handler from Mongrel::Rails::RailsHandler instead of Mongrel::HttpHandler and get the entire rails environment inside the handler ?

]]> By: links for 2007-05-11 « Bloggitation http://adam.blogs.bitscribe.net/2007/05/06/howto-custom-mongrel-handlers/#comment-6375 links for 2007-05-11 « Bloggitation Fri, 11 May 2007 00:21:18 +0000 http://adam.blogs.bitscribe.net/2007/05/06/howto-custom-mongrel-handlers/#comment-6375 [...] Custom Mongrel Handlers (tags: ruby mongrel web programming) [...] […] Custom Mongrel Handlers (tags: ruby mongrel web programming) […]

]]> By: adam http://adam.blogs.bitscribe.net/2007/05/06/howto-custom-mongrel-handlers/#comment-5970 adam Tue, 08 May 2007 23:17:57 +0000 http://adam.blogs.bitscribe.net/2007/05/06/howto-custom-mongrel-handlers/#comment-5970 Rick - Excellent, I wasn't even thinking about the fact that the mongrel process is actually executing in the same Ruby VM. What's the point of the mutex, though? The database certainly can handle simultaneous queries; is ActiveRecord not threadsafe? I though that ActionController was the only offender in that dept. In any case, I'll update the post with your improved version. Rick -

Excellent, I wasn’t even thinking about the fact that the mongrel process is actually executing in the same Ruby VM.

What’s the point of the mutex, though? The database certainly can handle simultaneous queries; is ActiveRecord not threadsafe? I though that ActionController was the only offender in that dept.

In any case, I’ll update the post with your improved version.

]]> By: rick http://adam.blogs.bitscribe.net/2007/05/06/howto-custom-mongrel-handlers/#comment-5960 rick Tue, 08 May 2007 21:49:05 +0000 http://adam.blogs.bitscribe.net/2007/05/06/howto-custom-mongrel-handlers/#comment-5960 One thing to keep in mind: since your handler is being run alongside a rails app, you shouldn't have to establish the connection of the ActiveRecord object. It should be the exact same class that's being used in the rails app. You also might want to put a mutex around your DB calls. http://pastie.caboo.se/59978 One thing to keep in mind: since your handler is being run alongside a rails app, you shouldn’t have to establish the connection of the ActiveRecord object. It should be the exact same class that’s being used in the rails app. You also might want to put a mutex around your DB calls.

http://pastie.caboo.se/59978

]]> By: rick http://adam.blogs.bitscribe.net/2007/05/06/howto-custom-mongrel-handlers/#comment-5957 rick Tue, 08 May 2007 21:41:30 +0000 http://adam.blogs.bitscribe.net/2007/05/06/howto-custom-mongrel-handlers/#comment-5957 The mongrel site includes my tutorial on using "upload progress gem":http://mongrel.rubyforge.org/docs/upload_progress.html, which is implemented as a simple mongrel handler. This is a good tutorial though. I'm working on a similar article for a minimal mongrel handler. Greg: the : in front of the yaml keys is so the values can be accessed with a symbol. yaml[:config_script] vs yaml['config_script']. The mongrel site includes my tutorial on using “upload progress gem”:http://mongrel.rubyforge.org/docs/upload_progress.html, which is implemented as a simple mongrel handler. This is a good tutorial though. I’m working on a similar article for a minimal mongrel handler.

Greg: the : in front of the yaml keys is so the values can be accessed with a symbol. yaml[:config_script] vs yaml[’config_script’].

]]> By: Adam @ Bitscribe » Comet with Rails + Mongrel http://adam.blogs.bitscribe.net/2007/05/06/howto-custom-mongrel-handlers/#comment-5872 Adam @ Bitscribe » Comet with Rails + Mongrel Tue, 08 May 2007 10:10:44 +0000 http://adam.blogs.bitscribe.net/2007/05/06/howto-custom-mongrel-handlers/#comment-5872 [...] In my last post I described how to create a mongrel handler. I said you might want to do this for optimization purposes, but my own interest came about in an attempt to solve the server-push problem with Rails. [...] […] In my last post I described how to create a mongrel handler. I said you might want to do this for optimization purposes, but my own interest came about in an attempt to solve the server-push problem with Rails. […]

]]> By: Greg http://adam.blogs.bitscribe.net/2007/05/06/howto-custom-mongrel-handlers/#comment-5767 Greg Mon, 07 May 2007 17:08:13 +0000 http://adam.blogs.bitscribe.net/2007/05/06/howto-custom-mongrel-handlers/#comment-5767 Hey Adam, nice post. This stuff is complicated enough that it helps to have lots of people's takes on it. Anyway, I can answer your question about loading a custom handler from a config script. I ran into the same problem. The keyword is, in fact, config_script, but in your yaml, you've got to precede it with a colon like this: --- :config_script: lib/mongrel_handlers/jsonp_handler.rb I don't know why it wants the colons, but that's what the examples look like on the Mongrel site and that's what works (treating them as hash keys?). Once you've got that setup, you can just load the conf file as normal: mongrel_rails start -C config/mongrel_conf.yml And mongrel will find the handler (you can see it in the printout if you launch mongrel without the -d flag). Hey Adam, nice post. This stuff is complicated enough that it helps to have lots of people’s takes on it. Anyway, I can answer your question about loading a custom handler from a config script. I ran into the same problem. The keyword is, in fact, config_script, but in your yaml, you’ve got to precede it with a colon like this:

—
:config_script: lib/mongrel_handlers/jsonp_handler.rb

I don’t know why it wants the colons, but that’s what the examples look like on the Mongrel site and that’s what works (treating them as hash keys?). Once you’ve got that setup, you can just load the conf file as normal:

mongrel_rails start -C config/mongrel_conf.yml

And mongrel will find the handler (you can see it in the printout if you launch mongrel without the -d flag).

]]>