We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
A clear and concise description of what you want to know.
I am implementing a standalone broker to be hosted in standalone Windows service process, and not hosted in IIS (not ASP.Net nor ASP.Net Core).
I need to support 3 classes of client nodes:
I need to support mixed clients (like browser based front-end node connecting to a .Net based self-hosted back-end node),
Let me summarize - no IIS anywhere in any configurations / scenarios. But need to support calls from the browser-based clients.
What should I override / overload / inject to support WesocketSharp-based Web sockets implementation of the client and server channels?
Thanks.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe your question
A clear and concise description of what you want to know.
I am implementing a standalone broker to be hosted in standalone Windows service process, and not hosted in IIS (not ASP.Net nor ASP.Net Core).
I need to support 3 classes of client nodes:
I need to support mixed clients (like browser based front-end node connecting to a .Net based self-hosted back-end node),
Let me summarize - no IIS anywhere in any configurations / scenarios. But need to support calls from the browser-based clients.
Which project is your question related to?
What should I override / overload / inject to support WesocketSharp-based Web sockets implementation of the client and server channels?
Thanks.
The text was updated successfully, but these errors were encountered: