You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 29b8c62
Browse filesBrowse the repository at this point in the historyBrowse files
/// Appends Events asynchronously to a stream if the stream version matches the <paramref name="expectedVersion"/>.
120
+
/// </summary>
121
+
/// <remarks>
122
+
/// When appending events to a stream the <see cref="ExpectedVersion"/> choice can
123
+
/// make a very large difference in the observed behavior. For example, if no stream exists
124
+
/// and ExpectedVersion.Any is used, a new stream will be implicitly created when appending.
125
+
///
126
+
/// There are also differences in idempotency between different types of calls.
127
+
/// If you specify an ExpectedVersion aside from ExpectedVersion.Any the Event Store
128
+
/// will give you an idempotency guarantee. If using ExpectedVersion.Any the Event Store
129
+
/// will do its best to provide idempotency but does not guarantee idempotency
130
+
/// </remarks>
131
+
/// <param name="stream">The name of the stream to append events to</param>
132
+
/// <param name="expectedVersion">The <see cref="ExpectedVersion"/> of the stream to append to</param>
133
+
/// <param name="events">The events to append to the stream</param>
134
+
/// <param name="userCredentials">The optional user credentials to perform operation with.</param>
135
+
/// <returns>If the operation succeeded and, if not, the reason for failure (which can be either stream version mismatch or trying to write to a deleted stream)</returns>
0 commit comments