Revision: 302
Author: julien.genestoux
Date: Tue Dec 22 13:25:05 2009
Log: Edited wiki page through web user interface.
http://code.google.com/p/pubsubhubbub/source/detail?r=302
Modified:
/wiki/AcceptingSubscriptionForPublishers.wiki
=======================================
--- /wiki/AcceptingSubscriptionForPublishers.wiki Tue Dec 22 13:24:29 2009
+++ /wiki/AcceptingSubscriptionForPublishers.wiki Tue Dec 22 13:25:05 2009
@@ -1,6 +1,6 @@
DRAFT PROPOSAL, UNFINISHED.
-#summary This describe a potential extension of the Core Protocol to
enable publisher to preemptively allow specific subscriptions.
+ This describe a potential extension of the Core Protocol to enable
publisher to preemptively allow specific subscriptions.
= Introduction =
@@ -12,7 +12,7 @@
= Details =
-Whenever a subscriber sends a subscription query to a hub, the hub should
fetch (or keep a cached version) to identify a "publisher endpoint" to
which it should forward the subscription parameters. The publisher MAY
define this publisher endpoint url, either via an HTTP header, or via a
specific <link> element inside the feed itself. If no publisher endpoint is
found, the hub must consider that the publisher accepts any subscription.
+Whenever a subscriber sends a subscription query to a hub, the hub should
fetch (or keep a cached version) to identify a "publisher endpoint" to
which it should forward the subscription parameters. The publisher MAY
define this publisher endpoint url, either via an HTTP header, or via a
specific `<link>` element inside the feed itself. If no publisher endpoint
is found, the hub must consider that the publisher accepts any subscription.
Once this "publisher endpoint" url is identified, before checking the
subscriber's intent, the hub should send a POST request the subscription
query to the "publisher endpoint", with a `hub.mode= accept`, as well as
the subscription parameters (`hub.topic` and `hub.callback`). The hub MUST
also include any additional parameters provided by the subscriber.
