Solid support and production-ready features

[radu-matei]

As I understand right now, SignalR will be supported for versions >= .NET Core 2.1 (and I assume .NET Standard 2.1), so I believe it is worth exploring and investigating issues that limit the use of this library in real workloads that will target .NET Core 1.x

Below is a set topics taken from the various issues and pull-requests here on GitHub, as well as additional features that might benefit users and should be updated according to work done in the repo (issues and pull-requests).

• [ ] User Context and Identity

• [ ] Distributed caching, Redis integration

• [ ] Full Framework target

• [ ] Dependency registration

• [ ] Encoding

• [ ] Logging

• [ ] Groups

• [ ] Performance

• [ ] Serialization

• [ ] Binary data transfer

• [ ] Connection state / Reconnection

• [ ] Samples

• [ ] Tests

• [ ] Investigate and merge existing pull-requests

• [ ] Documentation and contributing guidelines

• [ ] Automated release of NuGet

• [ ] Update Travis CI

• [ ] TypeScript / JavaScript client package release

• [ ] Other clients (Go, Java, others)

Please feel free to add any other issues, feature requests or suggestions and let's try to create a schedule (and discussion) for rational versioning of the packages (right now the versioning does not make much sense)

I already sent contributor invitation to some of you, please let me know if anybody else is interested.

CC @skorunka @discostu105 @RobSchoenaker @miker1423 @CodeGlitch0 @mikaelbr @ryanwersal @trydis (Please add other people in case I missed anyone)

[miker1423]

Hi! I would be pleased to help! where should we start?

[radu-matei]

@miker1423 - I think the first step would be matching the open PRs to the list above and prioritize.

I would start with the encoding PR.

[radu-matei]

@Henry00IS - just a heads-up on the things we want to have - would appreciate your thoughts on some of these.