Skip to content

Publishing transports as a separate package #172

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

Open
TheVeryStarlk opened this issue Mar 9, 2025 · 0 comments
Open

Publishing transports as a separate package #172

TheVeryStarlk opened this issue Mar 9, 2025 · 0 comments

Comments

@TheVeryStarlk
Copy link
Contributor

I'm not sure if I should create this issue in the ASP.NET Core repository or this one.

I want to use the socket transport that is present in both the ASP.NET Core and BedrockFramework repositories.

But the issue is, I'd need to reference the entirety of ASP.NET Core, or BedrockFramework for this just little part.
So, I thought it might be a good idea to publish a separate package that contains the implementation of transports (sockets, in memory, etc.).
Then it could be basically used by a connection factory of some sorts, something like ASP.NET Core's factory.

Chances are that I'm the only one who might benefit from this idea.
But, maybe, someone else would find this useful, so I made this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant