WebSockets enables two-way communication between the server and client.
ActionController::Live is merely an improvement of the HTTP Streaming functionality where the server will send HTML (or other data) down to the client part way through the request. So the server can send data, but not receive it from the client.
If you want to stream data to a client, then you can keep the connection open and just never "finish" the page. If you do this you'll have to be careful with concurrency etc, hence the requirement to use Thin/Rainbows/Puma not Unicorn.
A better comparison would probably be the new HTML5 Server-Sent Events (SSE) functionality. Though I'm not too familiar with that spec yet, so I can't comment on that.
ActionController::Live is merely an improvement of the HTTP Streaming functionality where the server will send HTML (or other data) down to the client part way through the request. So the server can send data, but not receive it from the client.
If you want to stream data to a client, then you can keep the connection open and just never "finish" the page. If you do this you'll have to be careful with concurrency etc, hence the requirement to use Thin/Rainbows/Puma not Unicorn.
A better comparison would probably be the new HTML5 Server-Sent Events (SSE) functionality. Though I'm not too familiar with that spec yet, so I can't comment on that.