-
Notifications
You must be signed in to change notification settings - Fork 1
Plan for official release #1
Comments
I'll appreciate that. I planned to use this fork in my future projects and make it more efficent and handy to use in .NET Core. I have not so much time for it right now but i planned to rewrite some key stuff in it and make this lib different from websocket-sharp according to .NET Core and C#6+ features like asyncs, tasks and other pretty stuff. Talking about release version, currently i have no roadmap or milestones for it. I planned to keep it in beta until it will be used on on several live projects, or at least one of my own projects. |
Keep up the good work. also I see the websocket-sharp project has lots of updates recently. Have you merged those into yours? Or what version did you branch from? |
@wsnell, thanks for attention for my project.
As you can see this project is not a fork of websocket-sharp. I have used official release sources as reference to make own implementation working with .NET Core for my own projects, but for now i have no time to work with it, websocket-core is stucks too.
Yep, it works as client and as server, but i'm not sure about SSL.
Yes, for now it's just take care to allow run code on .NET Core platform. |
With all the enthusiasm around .Net Standard and .Net Core 2.0, I was going to start doing what I believe you have already done by porting websocket-sharp and submitting a PR. I see you have a Nuget package in beta. Do you need any help with development and/or testing to produce an official 1.0 release?
The text was updated successfully, but these errors were encountered: