Sorry for the late reply! REST Hooks aren't really designed for browser consumption, you literally need a persistent connection to the browser to handle this.

Sorry for the late reply! REST Hooks aren't really designed for browser consumption, you literally need a persistent connection to the browser to handle this. For a quick example of a solution you could build: consider a Node server with Socket.IO. The client would work just like normal consuming REST APIs that return JSON, but the websocket would be an additional way to "update" the a Model or Collection in realtime. Perhaps something like Redis' PUBSUB would work as the core mechanism (perhaps in your PHP/Python/Ruby app you'd save to the db, ping PUB into Redis, the Node instance would SUB out the message and send it to any clients). I am sure you could get sub-second reaction times this way.