Timeline for Provide a streaming API instead of forcing API users to poll
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 29, 2017 at 23:24 | history | edited | Brock Adams | CC BY-SA 3.0 |
deleted 34 characters in body; edited tags
|
| Jan 10, 2012 at 20:07 | history | edited | Kevin Montrose |
edited tags
|
|
| Jan 10, 2012 at 18:01 | answer | added | Kevin Montrose | timeline score: 1 | |
| Jan 10, 2012 at 18:00 | history | edited | Kevin Montrose |
edited tags
|
|
| Jan 5, 2012 at 19:44 | comment | added | Jonathan. | @thejh, I don't know the details, I'm just saying what Kevin has previously said/implied. Also twitter rolled out their stream quite slowly, | |
| Jan 5, 2012 at 19:39 | comment | added | thejh | @Jonathan. What kinds of hardware resources are you concerned about? RAM? | |
| Jan 5, 2012 at 19:37 | comment | added | thejh | @Jonathan. I don't really think it'd take very long... at least if this API only gives you a few functions like "tag stream", "question stream" and "user stream" together with two or three options ("include full text" and "also alert on replies/comments" or so). | |
| Jan 5, 2012 at 19:00 | comment | added | Jonathan. | @thejh, as in hardware/bandwidth, and developer time, see how long it took for v2 of the API. | |
| Jan 5, 2012 at 18:49 | comment | added | thejh | @Jonathan. "resources"? as in hardware resources or as in developer time? | |
| Jan 5, 2012 at 18:19 | history | migrated | from meta.stackexchange.com (revisions) | ||
| Jan 5, 2012 at 18:12 | comment | added | thejh | In case your existing code isn't able to handle that so well, I'd offer building a stream server in node.js that can take all events, filter them and spit them out. :P | |
| Jan 5, 2012 at 17:54 | comment | added | thejh | @Shog9: Hmm, no, I haven't. Mhm... that's not streaming, but HTTP push notifications. Would probably work for me if I write some stuff around it, but a simple JSON stream like the one twitter offers is much easier to consume. Also, people behind NAT or with dynamic IPs would probably benefit from an API you can just connect to. | |
| Jan 5, 2012 at 17:44 | comment | added | Shog9 | Have you seen this? | |
| Jan 5, 2012 at 17:36 | history | asked | thejh | CC BY-SA 3.0 |