Create a deepstream.io client for .NET

[WolframHempel]

Create a deepstream.io client for .NET (e.g. in C#), that connects to deepstream via TCP and supports Authentication, Permissioning, Records, Events and RPCs.

Great resources to get started:
Writing a deepstream client
Deepstream Messaging structure
Detailed Cucumber Specs for Incoming and Outgoing messages (and associated behaviors)
Fully featured NodeJS Client as a reference

[schulz3000]

Hi,
I'm interested in creating a client for .NET
At the moment it was possible for me to connect, authenticate and subscribe to events with dotnet.
Will need some days to clean the code little bit up then I will publish a new repo with my try.

[yasserf]

Sounds awesome, looking forward to seeing it!

[WolframHempel]

I think the character codes for the split chars are a bit off. Its

exports.MESSAGE_SEPERATOR = String.fromCharCode( 30 ); // ASCII Record Seperator 1E
exports.MESSAGE_PART_SEPERATOR = String.fromCharCode( 31 ); // ASCII Unit Separator 1F

[schulz3000]

Basic Version of my DotNet Client for deepstream is available here: https://github.com/schulz3000/deepstreamNet

Contributions are welcome :)

[yasserf]

Nice!

Have you ever come across http://www.specflow.org/? It's apparently the cucumber equiv for .Net and that way you can use the same test suite as the js client

[schulz3000]

@yasserf heard about it but never worked with it before.
For now I added a special branch with it but it looks like that there are some problems with feature definitions because duplicated scenarios.

[yasserf]

The main work involved is via specifying a mock server which simulates deepstream. The individual steps themselves should just be proxies from the cucumber scenario to the actual API.

I didn't know duplicated scenarios fail in certain languages! That would certainly be a problem. Would it be okay if you dump the error message in here and I'll do some digging into how to rectify it? I would also be happy if you tell me how to run them.

[schulz3000]

@yasserf created an issue for it in the specs repo to split it from this issue, because it's a little bit of topic.
deepstreamIO/deepstream.io-client-specs#3

[kgodara]

Hey, I don't know exactly where progress with this is or how much has been completed, but I'd love to work on this if possible.

[WolframHempel]

@kgodara that'd be great. We're not .NET experts ourselves, but happy to help out as much as possible

[schulz3000]

Hi @kgodara,
the basics are working in my dotNet client for deepstream.io
If you want you can get in touch with it and implement the new methods "has" and "snapshot" for records, implement a better error handling or create some unit tests.