On Jan 27, 4:20 am, Pádraic Brady <[email protected]> wrote: > Problem with a fat ping is that there's no guarantee a Publisher can access > the entire feed content at the time a ping is made. Often the ping is sent > after publishing new content, before and not necessarily after the new feed > has been generated (which can occur on the next user request, including the > Hub's).
Could you please explain this a little more? You are saying the feed is virtual and only composed on access? How I've done this is before is a fat ping with an indication of how much data remains to be slurped up. If there is more data then the hub would return for more. Or the publisher can simply ping out data at a certain rate and the hub will never have to come back for more. > Pádraic Brady > > http://blog.astrumfutura.comhttp://www.survivethedeepend.com > OpenID Europe Foundation Irish Representative > > ________________________________ > From: todd hoff <[email protected]> > To: Pubsubhubbub <[email protected]> > Sent: Wed, January 27, 2010 5:22:26 AM > Subject: [pubsubhubbub] Possibility of fat ping from publisher to hub? > > My understanding is that there's a light ping from the publisher to > the hub. It would be convenient to use a fat ping here for the same > reason as a fat ping makes sense from the hub to the consumer. > Especially for low power devices the extra operations are a bit of a > drain.
