Whoa, nice find. I have to think Google Reader uses async because
I've still got no publisher diagnostics for my feedburner feeds. Even
after changing the url and resubscribing to avoid caching. No real-
time for http://pubsubhubbub.travisrss.x10.mx/?feed=rss2 either, but I
can see the diagnostics from lam3r4370's subscriber.
It seems to me that where sync works, async should work just as well
but not necessarily vice-verca if the host is limiting concurrent
connections. Strange...
On another note, I changed the hub at superfeedr.travisrss.x10.mx to
see how quickly Google Reader would subscribe to the new hub (updates
were working realtime before this change). I did this on Saturday and
still have no real-time updates. A work around is to resubscribe,
adding some useless parameters to the url. Google's caching seems to
be getting in the way here.
Julien,
Does SuperFeedr throttle polling frequency based on how often it sees
the feed change? I made a couple feeds that don't publish but just
rely on SuperFeedr's polling. One gets new items more frequently than
the other, and my logs show SuperFeedr polling them differently.