Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Puma, a fast concurrent web server for Ruby

puma.io

Post reply on HN
Print view View original

81–86 of 86 posts

Re: Puma, a fast concurrent web server for Ruby

#81

Post by moe »

FooBarWidget wrote: post #78
moe wrote: post #77

Earlier quoted context omitted.

I don't understand where your hostility comes from. From the dishonest spin that you put on everything you say. I wrote: That's equivalent to popping up shareware nag-screens into my face. You reply with: "popping up shareware nag-screens at random intervals" is completely false. There are absolutely no nag-screens in Phusion Passenger. These little 'misunderstandings' and strawmen add up. Consequently I won't even c…

I'm pretty sure you literally said "popping up shareware nag-screens at random intervals" instead of "that's equivalen to", but whatever, I'll take your word for it, in good faith, that you did not edit your post and that I read your post wrong. Like I said before: errors during redeploy are not supposed to happen even in the open source version, and if they do happen then we are very interested in fixing them. Pleas…

I'm pretty sure you literally said "popping up shareware nag-screens at random intervals" instead of "that's equivalen to", but whatever, I'll take your word for it, in good faith, that you did not edit your post and that I read your post wrong.

Wait, what...

You edited this line into your reply hours after you initially posted it. Hoping I would miss it or something?

And in this very edit you have the nerve to suggest I edit my comment after the fact to spin shit around?

Look at the position of the 'popping up' phrase in my post. How would saying it in any way other than it's written make any sense, syntactically?

And why would I claim passenger pops up literal nag screens, when everyone knows that's complete nonsense?

I do appreciate you showing your true colors in this thread. I'll make sure to link to it every time I run into one of your 'PR excursions' in the future.

Re: Puma, a fast concurrent web server for Ruby

#82

Post by sad »

justkez wrote: post #10
andrewhavens wrote: post #8

Earlier quoted context omitted.

Sounds more like a problem with your implementation. I'm pretty sure Puma can handle SSE just fine. Your implementation probably depends on EventMachine which is not baked in like it is with Thin.

I'm doing: content_type "text/event-stream" stream(:keep_open) { |out| settings.connections From Sinatra, which I assume is then deferring to EventMachine, courtesy of Thin. I'll see if there's a way of forcing EM directly in to the Stream setup...thanks for the pointer.

I created a sample app using Puma and Celluloid to work through similar troubles I was having with Sinatra's streams and Puma. If it helps, it's here: https://github.com/sdeming/cellfun. This does not use EventMachine, depending instead on Celluloid. I work primarily in JRuby and EventMachine has always tripped me up.

Re: Puma, a fast concurrent web server for Ruby

#83

Post by FooBarWidget »

moe wrote: post #81
FooBarWidget wrote: post #78

Earlier quoted context omitted.

I'm pretty sure you literally said "popping up shareware nag-screens at random intervals" instead of "that's equivalen to", but whatever, I'll take your word for it, in good faith, that you did not edit your post and that I read your post wrong. Like I said before: errors during redeploy are not supposed to happen even in the open source version, and if they do happen then we are very interested in fixing them. Pleas…

I'm pretty sure you literally said "popping up shareware nag-screens at random intervals" instead of "that's equivalen to", but whatever, I'll take your word for it, in good faith, that you did not edit your post and that I read your post wrong. Wait, what... You edited this line into your reply hours after you initially posted it. Hoping I would miss it or something? And in this very edit you have the nerve to sugge…

In other news: I've been asking other online communities as well in the hope of finding other users who have experienced the kind of problem you reported (http://www.reddit.com/r/ruby/comments/1lceav/ask_rreddit_doe...). Unfortunately I haven't received a single answer so far. Any feedback from you about the nature of the problem would be greatly appreciated.

Re: Puma, a fast concurrent web server for Ruby

#84

Post by tinco »

moe wrote: post #81
FooBarWidget wrote: post #78

Earlier quoted context omitted.

I'm pretty sure you literally said "popping up shareware nag-screens at random intervals" instead of "that's equivalen to", but whatever, I'll take your word for it, in good faith, that you did not edit your post and that I read your post wrong. Like I said before: errors during redeploy are not supposed to happen even in the open source version, and if they do happen then we are very interested in fixing them. Pleas…

I'm pretty sure you literally said "popping up shareware nag-screens at random intervals" instead of "that's equivalen to", but whatever, I'll take your word for it, in good faith, that you did not edit your post and that I read your post wrong. Wait, what... You edited this line into your reply hours after you initially posted it. Hoping I would miss it or something? And in this very edit you have the nerve to sugge…

hey moe, I sent you an e-mail on the e-mail address listed in your HN profile. Would you care to reply? I'd really like to talk to you about this..

Re: Puma, a fast concurrent web server for Ruby

#86

Post by FooBarWidget »

derengel wrote: post #85
FooBarWidget wrote: post #72

Earlier quoted context omitted.

Why not Node.js?

Because nodejs already has a high performance http server and a cluster module.

The point of serving Node through Phusion Passenger is not performance, but supervision, stability, robustness, security, multitenancy, etc. Although Phusion Passenger can increase performance by load balancing requests between multiple nodes. Please see https://github.com/phusion/passenger/wiki/Node.js for reasons to use Phusion Passenger with Node.

The cluster module is great, but it requires you to manage your processes yourself and to write your own load balancer. Phusion Passenger provides all this functionality for you for free, through a C++ core.

Post reply on HN