Hey, >From what side are you asking the question?
- From the publisher's side, well, the only way would be for you to implement some kind of track feature, where you basically remember what feeds users are susbcribed to and compare the "firehose" of all your updates to each of these queries to see which one matches. It's not easy, but it can be done. You may also use a Superfeedr hub as it know includes Track. - From the subscriber's perspective... well, you can just plug the feeds that you care about in a system which would do the polling on your behalf and push the updates to you when they happen, as if they were push. However, you will pay a latency price with this approach, based on the polling frequency of said provider. I hope this helps, let me know if I can do anything more :) Cheers! Ju On Fri, Oct 1, 2010 at 1:15 PM, gaztop79 <[email protected]> wrote: > I have a publishing system that produces atom feeds based on a complex > saved search. The saved search can be fairly unique for each of our > users and in reality no 2 users ends up querying the feed system in > the same way ie. the url for the feed will almost always be > different. > > At the moment we have between 10-20k users for these feeds using > polling for their updates (we also have a scheduling system which > pushes updates behind the scenes for specific clients but this > requires a fair amount of config work). > > Given that it is nigh on impossible for the publisher to tell which > feeds should be updated when something new is added, is there anyway > Pubsubhubbub could be used in this scenario without reverting to > polling each url for an update? Have you encountered this problem > before?
