Yep! This is the vision for Firehose. We have a few more details in mind for how to accomplish this:
1. Client binds to a Firehose resource, "/users/:id/polls"
2. Firehose proxies this request to the web app server, grabs the collection of polls upstream, and responds with this payload to the downstream Firehose client.
3. Firehose enters a mode where its listening for updates to items in the collection… so full CRUD (you need to keep the Firehose client informed of updates to items in the collection, so its more than create/delete).
4. Magic happens.
Singular resources are pretty easy!
The cool thing about this higher order streaming REST approach is that you could pretty easily hook this into Rails resources and make them push updates in realtime.
Let me know if you get serious about jumping into this and need some help getting started. I'd love to see more forks of Firehose that get close to this goal.