Receiving Commands with ActionCable
Let’s use ActionCable to deal with multiple attempts on the same ticket page by different browsers.
We'll cover the following...
ActionCable broadcast
The interactions work now, but we still need to catch the ActionCable broadcast if another browser on the same page holds a ticket. The tricky part here is that the display depends on a piece of client-side state, the “tickets to buy count” number, that the server won’t know when it makes the broadcast.
There are the three ways to make this work:
-
We could make the “tickets to buy count” number server-side state by having the server store it in a session or something similar and broadcast that information to other browsers via ActionCable ...