thin-ruby Google Group

Have You Seen

2010-01-03T23:57:33Z

Hi to my group friends! Have You seen this new video?
[link]

My wedding video

2010-01-01T20:29:47Z

Hi. This isour wedding video.
Happy New Year!
[link]

A joke

2009-12-31T17:29:09Z

O-ha-ha
What are they doing?
PS Just a joke, but so funny :)
[link]

The best new year video gift!

2009-12-30T23:25:08Z

This is nice) use it for friend or for family) [link]

Crazy moments in live tv news))

2009-12-28T18:16:30Z

ahah)))live tv news rules))))) [link]

Re: Thin without Proxy

2009-12-27T21:57:52Z

Yes, I run a lot of test applications in this manner.
Concurrent performance for synchronous application code.

Re: Thin without Proxy

2009-12-27T18:33:59Z

That's correct in most of cases.
So use an unique instance of thin :)

Re: Thin without Proxy

2009-12-27T17:55:11Z

On Sun, 27 Dec 2009 18:29:42 +0100
So I don't need to run a proxy in front of thin, if I want to run thin
on a single core machine? At the moment I don't see the advantage in
this, because caching is not very effective for my web application and
a non-caching proxy (e.g. for load balancing) doesn't seem to be

Re: Thin without Proxy

2009-12-27T17:29:42Z

This uses a event based model fro request handling over an unique Ruby
process. This means that by running an unique instance of Thin you don't take
advantages of a multi-core server.
By running a Thin cluster (N cores => N Thin instances) you get more
capability. But for this you obviously need a reverse proxy which dispatches

Thin without Proxy

2009-12-27T17:09:53Z

Hi,
could you please assess whether you can run thin without an upstream
proxy server like nginx? Are there any advantages of running multiple
thin instances with an upstream proxy?
I want to use sinatra with thin on a vps.
Regards,
Matthias-Christian

Short joke for You

2009-12-25T21:07:16Z

One short joke clip to cheer Your up!
[link]

Kids funny moments))

2009-12-25T17:56:21Z

yahooooooo)))i'm smiling all the day))) [link]

cheer up ;)

2009-12-20T08:54:34Z

Short fun clip, to cheer Your up.
[link]

Re: How to implement full async response (not just the body)

2009-12-19T01:51:49Z

I've detected a problem with the above code. My rack app uses Clogger so now
it looks like:
use ::Clogger, :logger => ::File.open("access.log", "ab")
if MyApp::CONFIG[:threaded]
run MyApp::Threaded
else
run MyApp
end
When MyApp::CONFIG[:threaded] is nil then Clogger printfs the access log to

thin-ruby Google Group

Have You Seen

My wedding video

A joke

The best new year video gift!

Crazy moments in live tv news))

Re: Thin without Proxy

Re: Thin without Proxy

Re: Thin without Proxy

Re: Thin without Proxy

Thin without Proxy

Short joke for You

Kids funny moments))

Top 10 funniest video anecdotes

cheer up ;)

Re: How to implement full async response (not just the body)