hub.secret already specifies a maximum length of "200 bytes".
A maximum length would be nice to define for verify_token, since it needs
to be stored by the hub if it's provided.
The previous revision of the spec defined secret and verify_token as
'bytes', and shouldn't be handled with any particular character encoding -
they are simply binary data, which the hub shouldn't be paying any attention
to the contents of.
On 3/8/2010 10:50 PM, Didier Durand wrote:
Hi there,
I am currently implementing PuSH for Google hub.
I am having an issue with current definition of verify token in parag
6.1. hub.verify_token is defined as "a subscriber-provided opaque
token". This doesn't specify what an opaque token is in max length,
allowed chars (alphanum only ? more ?), etc.
Wouldn't the spec benefit from those additionals details ? [Unless
"opaque token" is officially defined somewhere else and I missed it]
Same applies to hub.secret.
regards
didier
--
Jay Rossiter | Software Engineer/System Administrator
Pioneering RSS Advertising Solutions
[email protected] <mailto:[email protected]> | Phone: 503.896.6187 |
Fax: 503.235.2216
Website: www.pheedo.com <http://www.pheedo.com/> | RSS:
www.pheedo.info/index.xml <http://www.pheedo.info/index.xml>
