Ruben Bartelink

Stackoverflow.com is the recommended place for usage questions such as this. Please take the time to supply more complete information so people don't have to guess. Basic stuff like making...

>Therefore I asked if it is possible to overwrite this behavior from the outside Have you considered asking whether the lib would consider exposing a mechanism to expose its raw...

Aside from that I need the general `WriteResult` info, such an API would be fine (assuming an `int expectedVersion` param too). I guess one would call it `TryAppendToStreamAsync` The central...

Yes - Shaan is correct; as mentioned in #1626, this usage is very (too) read heavy, which is why it happens to be configured like this My interim solution will...

OK, this all makes sense, thanks for taking the time to lay it out. But... (don't hit me!) I'm still interested in saving the hop if possible as an optimization...

Yes, as Shaan says - the point is that in the case where you're not connected to the Master, there is no easy way to get the current state without...

TL;DR of the 'issues I run into' is that this is tweaking something that can already be made to work as it more directly models things I need to cater...

I agree with it being gRPC only - would love to see some solution for this as it removes a lot of messy workaround coding (having or connecting a separate...

The objective of the functionality is to deduplicate (handle idempotently) _concurrent_ appends - you'll find it does work if you run them on competing writers (which e.g. allows you to...

> to the event should be "to the event(s)" In other systems, this has been termed a `CommitId` I am absolutely not saying duplicates will happen - it explicitly deduplicates;...