-
Notifications
You must be signed in to change notification settings - Fork 10.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
[EPIC]: Bedrock Endgame #15005
Comments
Some of these might be able to check off or update? For example, "Introduce new Server API"? |
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process. |
Thanks for contacting us. |
why doesn't microsoft hire another 50 people to work on this which is used by millions of people |
or go to church and ask some of the folks whom retired from their fortran from the last century to volunteer to work on this project, it's like a toy for them |
Did you add your upvote? There's a sense that this is needed from the team but it would help if people upvoted and shared their use cases. I think this is a big missing piece from the .NET ecosystem and it's why I keep https://github.com/davidfowl/Bedrockframework alive |
Another standup update on topic along with status of System.IO.Connections would be nice 😄 |
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process. |
We have several legacy and third party custom TCP implementations that we integrate with and piping our own serialization in to the existing routing/controller infrastructure would simplify and consolidate a good amount of our implementations. It would also be nice to be able to take messages from a RabbitMQ or Kafka consumer, route by the payload to an action, then return a message result to drive ack/nack actions or advance offsets. |
IConnectionFactory
implementations for libuv and sockets transportsThe text was updated successfully, but these errors were encountered: