Skip to content

Add SSE section for Casper .NET SDK 3.x Introduced a new section on W… #98

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
davidatwhiletrue merged 1 commit into from
Mar 27, 2025
Merged

Add SSE section for Casper .NET SDK 3.x Introduced a new section on W… #98

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions Docs/Articles/WorkingWithSSE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
# Working with Server-Sent Events (SSE) in Casper .NET SDK 3.x

The new Casper Node **2.x** version introduced changes to the SSE protocol. To support these changes, the Casper .NET SDK has been updated to version **3.x**, introducing a new optional parameter `nodeVersion` in the `ServerEventsClient`.

## Creating `ServerEventsClient` for Node v2.x (Default)

When working with the new Casper Node version **2.x**, instantiate the `ServerEventsClient` without specifying the `nodeVersion`. The default value is set to `2`:

```csharp
var sse = new ServerEventsClient(eventIpAddress, localNetPort, nodeVersion: 1); // For versions 1.x

var sse = new ServerEventsClient(eventIpAddress, localNetPort); // The default value is 2
```