-
Notifications
You must be signed in to change notification settings - Fork 1k
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.
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
Implement DotNetty Transport #1356
Comments
We could build this as a stand alone PoC under up for grabs, just to get some effort going here. |
Added a fork of DotNetty here https://github.com/akkadotnet/DotNetty, incase MS drops the effort, we can continue it here. |
I'm working on implementing the missing pieces in DotNetty to make it wire-compatible with Helios - mostly a bunch of decoding stuff. Should take me another 12-16 hours worth of work (depending on how quickly I can get the testing infrastructure ported correctly) |
Took a while, but DotNetty should be wire-compatible with Helios now: Azure/DotNetty#40 Keep an eye on that PR. |
cc @SeanFarrow is going to take a stab at this |
Closed by #2444 |
Netty has been ported to .NET by MS and we are aiming to replace the current transport with a new transport built ontop of DotNetty.
https://github.com/Azure/DotNetty
Given the problems shown in #1355 and issues relating to message order I think we should step up our efforts on this one.
[edit] marking this critical as 300 msg/sec is simply not acceptable
The text was updated successfully, but these errors were encountered: