[ticker-dev] ticker-3.0 spec - Replace on Message ID

[Julian Boot]

Ian Lister wrote:

> It also requires clients to keep track of which subscriptions particular
> messages came in on, and to only accept replacements on those same
> subscriptions. Not a particularly significant issue I guess, just a minor
> complication.

well, in Java, Notification.getSource() returns the subscription, for
just this purpose.

combined with the ability to check if a notification was secure, I don't
see it as overly onerous for the developer to use keys to manage
authenticated replacements.

-J