Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pubsubhubbub best practices #62

Open
farski opened this issue Mar 14, 2017 · 1 comment
Open

Pubsubhubbub best practices #62

farski opened this issue Mar 14, 2017 · 1 comment
Labels

Comments

@farski
Copy link
Member

farski commented Mar 14, 2017

I think PuSH is generally still a good, lightweight technology that fits well with podcasting. But I also think some of the most common implementations of it leave a bit to be desired.

I'd like to add some language to the SM spec that clarifies expectations around some parts of PuSH implementation.

Two main points: feeds that do support PuSH notifications should start using the v4 HTTP headers to signify their support, and feeds that don't fully support PuSH should not include hub/topic headers/links.

@farski
Copy link
Member Author

farski commented Mar 14, 2017

Re: the second point, it's been my experience that Feedburner seems to add hub/topic links to every feed, even if support for PuSH is not enabled in feedburner for a given feed. And if you then try to subscribe to that topic, feedburner will accept the request, even though you'll never get a notification from it.

@farski farski added the idea label Mar 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant