search

ankurpiyush26 / pubsubhubbub

Automatically exported from code.google.com/p/pubsubhubbub
Other
1 stars 0 forks source link

Include the Hub's URL in the subscription verification request #42

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
SUMMARY:

From Padraic:

"This could be equally solved by requiring Hubs to send one additional
parameter with a confirm/feed update request:

hub.callback - the Hub's URL, i.e. to identify themselves more directly to
a Subscriber (at present it's all indirect)

In a generic implementation, the key used for storing a verify_token is
just a simple string: topic url + hub url (adding more doesn't make it any
more unique - except perhaps the mode depending on treatment of outstanding
reqs), normalised to a key that's safe to use for the current storage
medium. Other specific implementations might need additional context, but
that falls into the realm of a Subscribers special needs - something a
general implementation would address over the query string as optional (I
allow setting optional params in the Zend implementation)."

RELEVANT SECTION:  6.2

Original issue reported on code.google.com by bslatkin on 3 Aug 2009 at 4:21

GoogleCodeExporter commented 9 years ago 
Considering that subscribers may include querystring parameters in their 
callback
URLs, what is the benefit of this explicit functionality being baked into all 
hubs as
opposed to letting callers decide for themselves what reference information 
they want?

I'm leaning towards closing this issue as won't fix because I think it's easy 
to work
around now and minimizing the protocol's surface area is a good thing.

Original comment by bslat...@google.com on 8 Feb 2010 at 10:02

GoogleCodeExporter commented 9 years ago 
It's actually baked into the Zend Framework subscriber (as an example) though 
not
formally enabled in the sense described above yet (we support custom params but 
don't
use any as yet). So yes, it may be resolved as won't fix. Primarily I think the
original concern was more about Hub compliance and documentation of how to 
achieve
this effect. I'm about to do a review of subscribers/hubs for the next ZF 
version to
see just how many Hubs now support this (Superfeedr, for example, has been 
taking a
long long time to catch up with 0.2 and it's one of the large hubs for PSHB). 
The
documentation part isn't really a specification concern, just not sure how this
option can otherwise be communicated for implementors.

Original comment by padraic....@yahoo.com on 8 Feb 2010 at 10:26

GoogleCodeExporter commented 9 years ago

Original comment by the...@google.com on 26 Mar 2015 at 5:07