Skip to content
This repository has been archived by the owner on May 1, 2021. It is now read-only.

Add VSOCK socket support #4

Closed
wants to merge 1 commit into from
Closed

Add VSOCK socket support #4

wants to merge 1 commit into from

Conversation

elmarco
Copy link

@elmarco elmarco commented Jan 11, 2021

Gated as an optional feature, using vsock-rs.

Currently limited to Unix, but could be extended to Windows once the
AF_VSOCK API is bound.

Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Copy link
Collaborator

@taiki-e taiki-e left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since vsock-rs's major version is less than 1, it is basically unacceptable to have their types as public API. Also, I'm not clear about the maintenance status of that project.

So, I would recommend doing this as a separate crate for now.
I'm going to close this, but thanks @elmarco for the PR!

@taiki-e taiki-e closed this Jan 11, 2021
@elmarco
Copy link
Author

elmarco commented Jan 11, 2021

Since vsock-rs's major version is less than 1, it is basically unacceptable to have their types as public API. Also, I'm not clear about the maintenance status of that project.

So, I would recommend doing this as a separate crate for now.
I'm going to close this, but thanks @elmarco for the PR!

@taiki-e ok, can we make the connect() method public then?

@taiki-e
Copy link
Collaborator

taiki-e commented Jan 11, 2021

can we make the connect() method public then?

connect is an implementation detail and we wouldn't want to expose it. In fact, #5 will change connect's signature.
So, for now, I would suggest copying the #5 or master's connect function under the proper license.

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

Successfully merging this pull request may close these issues.

2 participants