Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Enhancement] Provide the ability to replace the remoting layer implementation for Proxy and Broker #9191

Open
1 task done
f1amingo opened this issue Feb 19, 2025 · 0 comments · May be fixed by #9192
Open
1 task done

[Enhancement] Provide the ability to replace the remoting layer implementation for Proxy and Broker #9191

f1amingo opened this issue Feb 19, 2025 · 0 comments · May be fixed by #9192
Labels
type/enhancement

Comments

@f1amingo
Copy link
Contributor

Before Creating the Enhancement Request

  • I have confirmed that this should be classified as an enhancement rather than a bug/feature.

Summary

Provide the ability to replace the remoting layer implementation for Proxy and Broker.

Motivation

This allows us to implement custom RemotingClient and RemotingServer to support a variety of network protocols.

Describe the Solution You'd Like

For the server side, by using a map to store multiple RemotingServers, and by adding new RemotingServer implementations, it is possible to support different network protocols.
For the client side, by adding a parameter and passing it through, it is possible to create new implementations of RemotingClientto support different network protocols.

Describe Alternatives You've Considered

None.

Additional Context

No response
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/enhancement
Projects
None yet
Milestone
No milestone
1 participant
@f1amingo