Subsequent subscription requests MUST override the previous subscription parameters

[GoogleCodeExporter]

SUMMARY:

Each subsequent call to the hub with mode.subscriber MUST *override*
the previous subscription for a specific (topic URL, callback) tuple.
I think that gives the behavior you want. Subscription = update in the
repeated case.

RELEVANT SECTION:  6.1

COMMENT/REQUEST:

From Tony:
> When a subscriber renews their subscription and supplies a new lease_seconds
> value, is the subscription updated with
>
> exactly the expiry time requested by the new lease_seconds value (if it's
> acceptable to the hub)
> the most-future of the old expiry time and the newly requested expiry time
>
> ?
>
> (I'm guessing the *least-future* of the two isn't even worth considering ;-)
> )
>
> If the latter, subscribers have no way of shortening their lease. For now
> I'm going to implement the former.

Original issue reported on code.google.com by bslatkin on 14 Jul 2009 at 5:14

[GoogleCodeExporter]

Original comment by bslatkin on 27 Aug 2009 at 3:43

• Added labels: spec0.2

[GoogleCodeExporter]

Addressed in 0.2

Original comment by bslatkin on 2 Sep 2009 at 1:21

• Changed state: Fixed