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 current limitation of dmsg applications is the need for a dmsg client to be written into the application.
what I propose is an application which does the following:
<dmsg-pk>:<port>
in this way, external applications can be accessed over dmsg without needing to be rewritten to include a dmsg client.
this can be made to use skywire routes via the proxy if a proxy configuration for the dmsg client is allowed / implemented as specified in #233
The text was updated successfully, but these errors were encountered:
this was implemented in #236
Sorry, something went wrong.
No branches or pull requests
a current limitation of dmsg applications is the need for a dmsg client to be written into the application.
what I propose is an application which does the following:
<dmsg-pk>:<port>
in this way, external applications can be accessed over dmsg without needing to be rewritten to include a dmsg client.
this can be made to use skywire routes via the proxy if a proxy configuration for the dmsg client is allowed / implemented as specified in #233
The text was updated successfully, but these errors were encountered: