Me too. Luckily I was monitoring some lengthly database operations, nothing customer-facing.
Sometimes the streaming reply worked, sometimes it hung, sometimes it crashed. After a few days of pain I rewrote it in Node (which is a shame since the rest of the code is in Ruby). Worked 100% first try, no handholding.
I don't care whose fault it is. ActionController::Live should be turned off until it's more stable.
I imagine the Rails team wants to make this more robust but I think there's some bad design decisions in Rack that are preventing ActionController::Live from being as robust as it could.
Comments
It is very half-baked. I put it into a production system and had tons of headaches.
Me too. Luckily I was monitoring some lengthly database operations, nothing customer-facing.
Sometimes the streaming reply worked, sometimes it hung, sometimes it crashed. After a few days of pain I rewrote it in Node (which is a shame since the rest of the code is in Ruby). Worked 100% first try, no handholding.
I don't care whose fault it is. ActionController::Live should be turned off until it's more stable.
I imagine the Rails team wants to make this more robust but I think there's some bad design decisions in Rack that are preventing ActionController::Live from being as robust as it could.
Yep, cf. "I firmly believe Rack is shackling progress for Ruby on the web." - @tenderlove
https://twitter.com/tenderlove/status/443893529010393089
it's pretty hard to do something better with the current status of Rack