News for hackers. Stuff that matters.
Re:Live Streaming in Rails 4.0 by masklinn on Monday July 30, 2012 @04:59PM (#4314656)
> I want to write to the socket.

That's what you do when you yield to the each's block. It's not like the caller calls each multiple times when it wants new data, he calls `each` once and you feed it data via the block it provides.

> Somehow data must be fed to the `each` function

Just as it "must be" fed to the `write` in your examples.

Re:Live Streaming in Rails 4.0 by tenderlove on Monday July 30, 2012 @05:13PM (#4314718)
> > I want to write to the socket.

> That's what you do when you yield to the each's block.

No IO object in ruby uses the `each` method for writing.

Re:Live Streaming in Rails 4.0 by masklinn on Tuesday July 31, 2012 @04:32AM (#4316272)
You are mistaken and confused. All IO objects in Ruby use `each` for writing out, non-IO objects use something else to write to IO objects. But from an IO object's perspective, that's a read.

Rack responses are IO objects, so they use #each to write data out. That's perfectly coherent.

Re:Live Streaming in Rails 4.0 by bascule on Tuesday July 31, 2012 @01:25PM (#4318497)
Responding to #each is neither a necessary or sufficient property of Ruby IO objects. You are mistaken and confused.

Don't believe me? Let's undefine #each on the metaclass of an IO object and see what happens. Guess what: it still works!

https://gist.github.com/3218710