The spec allows for multiple hubs, but all of the hubs should be
distributing the same content, and all of them should respond to the published
self link.
In the case of WP, when FB adds their hub information, they also change
the self link. If a user were to work in a top-down priority for hub
subscription, they hit an error. WP is the first hub listed in the feed, but
it refuses subscriptions for the Feedburner self-link. (As expected, since
it's a private hub.)
The subscriber thus has to be willing and able to move on to the next hub
in the list and attempt to subscribe there.
The problem isn't that a user may be getting content directly from the
source. If that was the case, the WP hub would work perfectly because the
content hasn't been modified by an outside source and can subscribe to the
WP-self link. The issue at hand is really how proxy services should handle
feeds that are already hub-enabled when they make their modifications, because
it adds two possible issues; the first is what I described - that the first
hub won't allow subscriptions because it's not authoritative for that URL, and
the second is that it DOES allow subscriptions, but it provides the wrong
content.
The second issue is the worst of the two /*if*/ the client subscribes to
both hubs, because they will both provide different sets of content, which
will cause duplication in the client's dataset.
On 3/4/2010 2:26 PM, Matthew Terenzio wrote:
> Some time back there was discussion about having more than one hub in the
> feed for backup etc. What was the consensus there?
>
> I remember it being suggested that the order they were listed might indicate
> the priority. Might that work here?
>
> Am I correct in my understanding that this is only an issue with hosted
> solutions that provide a hub and allow their users to use a third part proxy
> like Feedburner?
>
> I mean, the users of feedburner must get SOME traffic on their native feeds
> in the polling world. They've lived with that. Why can't they live with this?
>
> I haven't thought that through much, just asking.
--
Jay Rossiter | Software Engineer/System Administrator
Pioneering RSS Advertising Solutions
[email protected] <mailto:[email protected]> | Phone: 503.896.6187 |
Fax: 503.235.2216
Website: www.pheedo.com <http://www.pheedo.com/> | RSS:
www.pheedo.info/index.xml <http://www.pheedo.info/index.xml>
<<inline: pheedo.gif>>
