From: yermej <yermej@...>
Date: 2010-07-16T00:45:04+09:00
Subject: Re: Ruby best practice for "always on" app/service?

On Jul 14, 11:53 pm, David Masover <ni...@slaphack.com> wrote:
> On Wednesday, July 14, 2010 05:10:06 pm yermej wrote:
> > Is there a more accepted way to handle this? Something where the web
> > service client would be always running and somehow listening for a
> > request?
>
> How is that different than what you're doing?
>
> I suppose something like mod_ruby might listen without a worker running, then
> instantiate your app when you get a request.

That's how mod_ruby and WEBrick work.

I wasn't entirely sure of what my question was when I started this
thread. A couple replies have helped me figure out what else to ask
about. I'll definitely look into the Rack-based options.

> But many other servers simply
> embed themselves into a running process -- that IS your app always running,
> waiting for a request.

This is what I meant by "always on". Probably not the right term, but
it was a starting point.

I was also not detailed enough about what I'm doing. In my reply to
Richard's reply, I'll bring up my other concern which is how to handle
a situation where my proxy/adapter app is being called by other apps
on the same server rather than as a web service -- more of an
interprocess communication issue, I guess. However, for actual web
services, I now know to look to Rack-based technologies.

Thanks for the reply.
Jeremy