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
Copy file name to clipboardExpand all lines: README.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,41 +43,41 @@ confluent-kafka-dotnet is distributed via NuGet. We provide five packages:
43
43
To install Confluent.Kafka from within Visual Studio, search for Confluent.Kafka in the NuGet Package Manager UI, or run the following command in the Package Manager Console:
To add a reference to a dotnet core project, execute the following at the command line:
50
50
51
51
```
52
-
dotnet add package -v 2.3.0-RC3 Confluent.Kafka
52
+
dotnet add package -v 2.3.0-RC4 Confluent.Kafka
53
53
```
54
54
55
55
Note: `Confluent.Kafka` depends on the `librdkafka.redist` package which provides a number of different builds of `librdkafka` that are compatible with [common platforms](https://github.com/edenhill/librdkafka/wiki/librdkafka.redist-NuGet-package-runtime-libraries). If you are on one of these platforms this will all work seamlessly (and you don't need to explicitly reference `librdkafka.redist`). If you are on a different platform, you may need to [build librdkafka](https://github.com/edenhill/librdkafka#building) manually (or acquire it via other means) and load it using the [Library.Load](https://docs.confluent.io/current/clients/confluent-kafka-dotnet/api/Confluent.Kafka.Library.html#Confluent_Kafka_Library_Load_System_String_) method.
56
56
57
57
### Branch builds
58
58
59
-
Nuget packages corresponding to all commits to release branches are available from the following nuget package source (Note: this is not a web URL - you
59
+
Nuget packages corresponding to all commits to release branches are available from the following nuget package source (Note: this is not a web URL - you
60
60
should specify it in the nuget package manager):
61
-
[https://ci.appveyor.com/nuget/confluent-kafka-dotnet](https://ci.appveyor.com/nuget/confluent-kafka-dotnet). The version suffix of these nuget packages
62
-
matches the appveyor build number. You can see which commit a particular build number corresponds to by looking at the
61
+
[https://ci.appveyor.com/nuget/confluent-kafka-dotnet](https://ci.appveyor.com/nuget/confluent-kafka-dotnet). The version suffix of these nuget packages
62
+
matches the appveyor build number. You can see which commit a particular build number corresponds to by looking at the
For a step-by-step guide and code samples, see [Getting Started with Apache Kafka and .NET](https://developer.confluent.io/get-started/dotnet/) on [Confluent Developer](https://developer.confluent.io/).
68
+
For a step-by-step guide and code samples, see [Getting Started with Apache Kafka and .NET](https://developer.confluent.io/get-started/dotnet/) on [Confluent Developer](https://developer.confluent.io/).
69
69
70
-
You can also take the free self-paced training course [Apache Kafka for .NET Developers](https://developer.confluent.io/learn-kafka/apache-kafka-for-dotnet/) on [Confluent Developer](https://developer.confluent.io/).
70
+
You can also take the free self-paced training course [Apache Kafka for .NET Developers](https://developer.confluent.io/learn-kafka/apache-kafka-for-dotnet/) on [Confluent Developer](https://developer.confluent.io/).
71
71
72
-
Take a look in the [examples](examples) directory and at the [integration tests](test/Confluent.Kafka.IntegrationTests/Tests) for further examples.
72
+
Take a look in the [examples](examples) directory and at the [integration tests](test/Confluent.Kafka.IntegrationTests/Tests) for further examples.
73
73
74
-
For an overview of configuration properties, refer to the [librdkafka documentation](https://github.com/edenhill/librdkafka/blob/master/CONFIGURATION.md).
74
+
For an overview of configuration properties, refer to the [librdkafka documentation](https://github.com/edenhill/librdkafka/blob/master/CONFIGURATION.md).
75
75
76
76
### Basic Producer Examples
77
77
78
78
You should use the `ProduceAsync` method if you would like to wait for the result of your produce
79
79
requests before proceeding. You might typically want to do this in highly concurrent scenarios,
80
-
for example in the context of handling web requests. Behind the scenes, the client will manage
80
+
for example in the context of handling web requests. Behind the scenes, the client will manage
81
81
optimizing communication with the Kafka brokers for you, batching requests as appropriate.
82
82
83
83
```csharp
@@ -111,8 +111,8 @@ class Program
111
111
```
112
112
113
113
Note that a server round-trip is slow (3ms at a minimum; actual latency depends on many factors).
114
-
In highly concurrent scenarios you will achieve high overall throughput out of the producer using
115
-
the above approach, but there will be a delay on each `await` call. In stream processing
114
+
In highly concurrent scenarios you will achieve high overall throughput out of the producer using
115
+
the above approach, but there will be a delay on each `await` call. In stream processing
116
116
applications, where you would like to process many messages in rapid succession, you would typically
// Note: The AutoOffsetReset property determines the start offset in the event
@@ -258,7 +258,7 @@ to integrate with Kafka. For more information, refer to the [3rd Party Libraries
258
258
259
259
### Confluent Cloud
260
260
261
-
For a step-by-step guide on using the .NET client with Confluent Cloud see [Getting Started with Apache Kafka and .NET](https://developer.confluent.io/get-started/dotnet/) on [Confluent Developer](https://developer.confluent.io/).
261
+
For a step-by-step guide on using the .NET client with Confluent Cloud see [Getting Started with Apache Kafka and .NET](https://developer.confluent.io/get-started/dotnet/) on [Confluent Developer](https://developer.confluent.io/).
262
262
263
263
You can also refer to the [Confluent Cloud example](examples/ConfluentCloud) which demonstrates how to configure the .NET client for use with
0 commit comments