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

feat: switch between using UnixConn and TCPConn for WASI #68

Open
gaukas opened this issue Jun 7, 2024 · 2 comments
Open

feat: switch between using UnixConn and TCPConn for WASI #68

gaukas opened this issue Jun 7, 2024 · 2 comments
Assignees
@gaukas
Labels
enhancement New feature or request wontfix This will not be worked on

Comments

@gaukas
Copy link
Contributor

gaukas commented Jun 7, 2024

Currently both transport/v0 and transport/v1 hardcodes TCPConn for local WASI usage (caller <==> WATM) and UnixConn is unused. It would be potentially interesting to allow the use of UnixConn by caller's choice.
@gaukas gaukas added the enhancement New feature or request label Jun 7, 2024
@gaukas gaukas self-assigned this Jun 7, 2024
@gaukas
Copy link
Contributor Author

gaukas commented Jun 7, 2024

This change potentially requires some more changes to be made to our dependency, the WebAssembly runtime wazero, given currently wazero supports only TCPConn among all net.Conn implementations.

@gaukas gaukas mentioned this issue Jun 7, 2024
Open
@gaukas gaukas added the wontfix This will not be worked on label Jun 7, 2024
@gaukas
Copy link
Contributor Author

gaukas commented Jun 7, 2024

Blocked until #69 is resolved and result showing UnixConn prevails under certain circumstances when comparing to TCPConn.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gaukas gaukas

Labels
enhancement New feature or request wontfix This will not be worked on
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gaukas