[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Andy Bierman <email@example.com> wrote:
> Sharon Chisholm wrote:
> > Then we are discussing specific behaviour of the replayLogStartTime
> > object. Nothing in this object indicates whether or not functionality is
> > supported. It only tells you how much stuff is available in the log at
> > this point in time.
> > I don't think we want it conditional like Martin indicated. I think we
> > need to pick one of
> > A. It is the timestamp of the earliest notification in the log
> > B. It is the timestamp of the start of the log.
> Agreed -- it should be (A), since from a NETCONF manager POV,
> there is no difference between no replay log and an empty replay log.
Yes, IMO B doesn't make much sense. With A, the manager can see if it
has missed any notifications.
So we come back to my original issue. If it's not conditional, what is
1) if replay is not supported on the stream?
2) if replay is supported on the stream but there are no entries in
One solution is of course to provide some kind of dummy value, but I
don't see the point in that.
Another solution, which is my suggestion, is to make the object
conditional - in these cases the object instance will simply not be
to unsubscribe send a message to firstname.lastname@example.org with
the word 'unsubscribe' in a single line as the message text body.