3 ms·
Of course, making those feeds PubSubHubbub would be ideal, so that my dear reader wouldn't have to poll them all the time =) And since now PubSubHubbub is conte
by julien 16y ago
Of course, making those feeds PubSubHubbub would be ideal, so that my dear reader wouldn't have to poll them all the time =) And since now PubSubHubbub is content agnostic (http://news.ycombinator.com/item?id=1981234 http://news.ycombinator.com/item?id=1981234), it would work for the calendar feeds too!
- simonw 16y agoI did think about PubSubHubbub for this, but implementing pings was a bit fiddly - a conference appears on the django-in-london feed only after the django tag has been added for example, but that also implies it appearing in the django-in-uk feed. Since it doesn't really matter if you hear about a new conference within seconds, minutes, hours or even days I decided it wasn't worth doing PubSubHubbub for the initial launch of this feature.
- julien 16y agoYup... I agree with the cause : " it doesn't really matter if you hear about a new conference within seconds, minutes, hours or even days", but not with the consequence! PubSubHubbub is not about time, but about push (timeliness is a consequence). By having a push mechanism, you just allow for updates to propagate to any kind of application, rather than have them all poll the resources endlessly, wasting their resources, your ressources and eventually just making it not worth. You want other to consume your content. Make their life easier :)