Revision: 381
Author: codemonkeydan
Date: Wed Jul 14 13:16:20 2010
Log: Edited wiki page through web user interface.
http://code.google.com/p/pubsubhubbub/source/detail?r=381
Modified:
/wiki/HubsAndFeedProxies.wiki
=======================================
--- /wiki/HubsAndFeedProxies.wiki Wed Jul 14 13:15:58 2010
+++ /wiki/HubsAndFeedProxies.wiki Wed Jul 14 13:16:20 2010
@@ -8,8 +8,7 @@
* The hub spec assumes that every URL resolves to the same feed content
for all subscribers; but publishers using feed proxies often conditionally
redirect their feed URL to their proxied feed URL for all user agents
except the feed proxy, which receives their source feed. (This allows them
to continue serving their source feed in its original URL to the proxy, and
serve the proxied version of the feed to subscribers that were already
subscribed to the URL before it was proxied.) Since the feed proxy gets the
source feed and everyone else gets the proxied feed, it's not possible for
the hub to have both versions of the feed under the same URL.
* Publishers who have set up conditional redirects as described above
typically will redirect hubs to the proxied feed as well; so the feed proxy
can't get updates to the source feed from the hub. On the other hand, if
the conditional redirect does not apply to the hub, then any subscriber to
the hub will get the non-proxied version of the feeds (which isn't what the
publisher wants.)
- * A single feed may wind up being served under multiple URLs by the feed
proxy; an update to the proxied feed should cause updates to subscribers of
all of these URLs. But the feed proxy generally speaking doesn't know what
all these URLs are, and shouldn't have to send pings for all of them. Note
that this problem isn't unique to feed proxies; all
-platforms that support serving a single feed under different URLs share
this problem.
+ * A single feed may wind up being served under multiple URLs by the feed
proxy; an update to the proxied feed should cause updates to subscribers of
all of these URLs. But the feed proxy generally speaking doesn't know what
all these URLs are, and shouldn't have to send pings for all of them. Note
that this problem isn't unique to feed proxies; all platforms that support
serving a single feed under different URLs share this problem.
* A source feed may contain a hub link that can be used to subscribe to
the source feed; but there may be problems if that hub link is included in
the proxied feed, since the source feed's hub may not receive the
appropriate updates from the feed proxy, or may not be set up to give
access to feeds under the proxied feed domain.
Below I'll discuss the approach by which we are addressing these problems
in FeedBurner and the reference hub. We believe this approach can be used
by other hubs and feed proxies to solve these problems.
