4 ms·

I’ve wondered if this existed, to simplify writing a system that parses and processes RSS. Frankly I’d go a bit further and spit out events, so people can code

I’ve wondered if this existed, to simplify writing a system that parses and processes RSS. Frankly I’d go a bit further and spit out events, so people can code “give me the next entry” without having to mess with polling lots of rss endpoints. Just tell me when there’s a new entry. Or turn it into a web hook so you just code the parsing, and delivery is outsourced. Polling for changes is a terrible design. The source has to serve data on repeat to every reader that is set up to check once every week/day/hour/minute. At the very least have a distributed cache that is set to return only the entries created after generally agreed timestamps. (Please tell me that exists now, or why it’s a bad idea.)

aflukasz 2y ago
> (Please tell me that exists now, or why it’s a bad idea.) Regarding the only-after semantics: - HTTP has "Delta encoding in HTTP": https://www.rfc-editor.org/rfc/rfc3229 https://www.rfc-editor.org/rfc/rfc3229 (2002), - usage for feeds proposed in 2004: https://bobwyman.typepad.com/main/2004/09/using_rfc3229_w.html https://bobwyman.typepad.com/main/2004/09/using_rfc3229_w.ht..., - some (not so) recent discussion (2017): https://www.ctrl.blog/entry/feed-delta-updates.html https://www.ctrl.blog/entry/feed-delta-updates.html + https://news.ycombinator.com/item?id=26091489 https://news.ycombinator.com/item?id=26091489 (zero comments). Adoption (or lack there of) is a different story. I guess the main issue is that it puts more work on the publisher side, in particular requires dynamic aspect when generating the response.