nats-io / nats.net.v2

nats-io/nats-architecture-and-design#261

@mtmk as per slack conversation, I'll like to give this one a shot.

Initial idea:

NatsKvOpts.cs
Would add ResumeAtRevision int prop to NatsKVWatchOpts (document it to be "The revision to start from, if set to 0 (default) this will be ignored"

nats.net.v2/src/NATS.Client.KeyValueStore/NatsKVOpts.cs

Line 43 in dcfaac1

public Func<CancellationToken, ValueTask<bool>>? OnNoData { get; init; }

NatsKVWatcher.cs
It's using the _sequenceStream here

nats.net.v2/src/NATS.Client.KeyValueStore/Internal/NatsKVWatcher.cs

Line 353 in dcfaac1

var sequence = Volatile.Read(ref _sequenceStream);

And I was thinking about setting _sequenceStream = opts.ResumeAtRevision here https://github.com/nats-io/nats.net.v2/blob/main/src/NATS.Client.KeyValueStore/Internal/NatsKVWatcher.cs#L78

@niklasfp looking at this a bit closer I think it's good. Setting the _sequenceStream = opts.ResumeAtRevision in NatsKVWatcher.ctor should work since it will treacle down to the consumer create request down below and also should be updated as expected on reconnects. feel free to open a PR when you're ready and have time. thank you 💯

@niklasfp looking at this a bit closer I think it's good. Setting the _sequenceStream = opts.ResumeAtRevision in NatsKVWatcher.ctor should work since it will treacle down to the consumer create request down below and also should be updated as expected on reconnects. feel free to open a PR when you're ready and have time. thank you 💯

For future reference and history, setting the sequence in the ctor was not an option because of the way watchers gets re-created.

KV ResumeAtRevision option for watches