WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Pubsubhubbub best practices #62

@farski

Description

@farski

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions