Re: [pubsubhubbub] Is PuSH 0.4 the spec to work to?

48 views
Skip to first unread message

Percy Baker

unread,
May 16, 2013, 6:33:30 PM5/16/13
to pubsub...@googlegroups.com
remove from your email loist,

Percy Baker


On Thu, May 16, 2013 at 4:24 PM, James Clemence <ja...@jvc26.org> wrote:
I'm just working on a project which is based around PuSH, and was keen to know what the current spec is that the appspot hub works to? Is 0.4 now considered the defacto standard (whilst still a working draft?) or do people work to 0.3? - I notice some of the old implementation has been scrapped between 0.3 and 0.4 (read sync/async, the generally defunct verify_token parameter etc. and wouldn't want to start work on something which wasn't yet mainstream!

Thanks!

--
 
---
You received this message because you are subscribed to the Google Groups "Pubsubhubbub" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pubsubhubbub...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Roman

unread,
May 17, 2013, 6:24:01 AM5/17/13
to pubsub...@googlegroups.com
Hi James,

Yes, the 0.4 spec is the de facto standard. We are going to make an announcement some time in June.

The Google hub still supports the 0.3 spec for backward compatibility.

Roman.

James Clemence

unread,
May 17, 2013, 12:02:24 PM5/17/13
to pubsub...@googlegroups.com
On Friday, 17 May 2013 11:24:01 UTC+1, Roman Perepelitsa wrote:
Yes, the 0.4 spec is the de facto standard. We are going to make an announcement some time in June.

The Google hub still supports the 0.3 spec for backward compatibility.

Excellent - thanks for your help! 

Are there any features which are considered particularly important in the transition phase to support between the two, or would you recommend just coding to 0.4?

Thanks 

Roman

unread,
May 21, 2013, 8:30:02 AM5/21/13
to pubsub...@googlegroups.com
My apologies for the delay in response.

The most robust approach is to only use features that exist in both 0.3 and 0.4 specs. For example, don't use "sync" subscription requests because 0.4 doesn't have them and don't reject distribution requests from the hub if they don't have the Link HTTP header because 0.3 doesn't have them.

In short, follow the robustness principle: Be conservative in what you send, be liberal in what you accept.

Roman.
Reply all
Reply to author
Forward
0 new messages