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

Move "implementing a resource host" out of components book #144

Open
itowlson opened this issue Jun 11, 2024 · 2 comments
Open

Move "implementing a resource host" out of components book #144

itowlson opened this issue Jun 11, 2024 · 2 comments

Comments

@itowlson
Copy link
Collaborator

As part of #140 I captured some information about implementing a host that exported resources to a guest. This isn't really the right venue for that, because this book is about writing and using components, not about implementing Wasmtime hosts, but I didn't want to lose the info. See thread at #140 (comment).

When we can locate a better place for it, we should move it to that place. It's not quite clear if the Wasmtime book is suitable but that's probably the first port of call.

The affected section is "Implementing and exporting a resource implementation in a host" in src/language-support/rust.md.

@kate-goldenring
Copy link
Collaborator

Could the scope of the book be expanded to be about writing and using guest and host components? I don't fully see why host components cannot be in scope for the book.

@rylev
Copy link
Collaborator

rylev commented Jun 13, 2024

I think the issue is that this requires picking favorites when it comes to a component compatible runtime. Implementing component support in a host is tied very closely with the runtime used, and so the information presented isn't really general knowledge about components but rather a tutorial on how to use that runtime.

That's why I think it's fine to mention it in this book, but we should link to runtime specific tutorials elsewhere.

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

3 participants