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.

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

Python host vs target C implementations #53

Open
sammyj85 opened this issue Jan 25, 2024 · 0 comments
Open

Python host vs target C implementations #53

sammyj85 opened this issue Jan 25, 2024 · 0 comments

Comments

@sammyj85
Copy link

sammyj85 commented Jan 25, 2024

The host implementation appears to be only provided in Python, and the target implementation is provided in C.

It appears based on some comments in the Python implementation that is an asymmetrical (different) implementation to the C implementation.

We are not interested in running Python on the host, but we want to run C. To some degree it seems to work with the C implementation on the host and target. What features or aspects of the protocol are we missing out on by running the target implementation on the host?

Is it a common enough use case to want C for the host implementation that the C implementation will fully support the host as well as target?

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

No branches or pull requests

1 participant