|
Something that's not addressed anywhere in the spec currently is protocol versioning. I think it becomes fairly evident that as the protocol changes (in some suggestions, quite drastically, such as using atom:id instead of atom:link[rel=self] for feed identifiers), things could become very out of sync between what subscribers and hubs support. In my opinion, there's a real need/benefit to adding an "X-PuSH-Version:" (revise naming as you will) header for all outgoing connections. The receiving host should respond appropriately (415 Unsupported Media Type ?) if a version is unsupported. This would alleviate confusion once the protocol starts to diverge from its current state, and different specs become incompatible with each other. --
![]() Jay Rossiter | Software Engineer/System Administrator Pioneering RSS Advertising Solutions [email protected] | Phone: 503.896.6187 | Fax: 503.235.2216 Website: www.pheedo.com | RSS: www.pheedo.info/index.xml |
- [pubsubhubbub] Protocol versioning Jay Rossiter
- [pubsubhubbub] Re: Protocol versioning Pádraic Brady
- [pubsubhubbub] Re: Protocol versioning Jay Rossiter
- [pubsubhubbub] Re: Protocol versioning Martin Atkins

