-
Notifications
You must be signed in to change notification settings - Fork 28
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
Links should be cached #206
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this has been closed too eagerly, please feel free to tag a maintainer so we can keep working on the issue. Thank you for contributing to wasmCloud! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this has been closed too eagerly, please feel free to tag a maintainer so we can keep working on the issue. Thank you for contributing to wasmCloud! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this has been closed too eagerly, please feel free to tag a maintainer so we can keep working on the issue. Thank you for contributing to wasmCloud! |
This is a follow on to #203 and #204. Looking up links can take up a bunch of time and bandwidth. Wadm should fetch the initial list of linkdefs from a host and then update the local cache when
LinkdefSet
andLinkdefDeleted
events come in. This can all be backed behind an implementation of theLinkSource
traitNOTE: This would also be nice for claims, but we query claims a lot less and there isn't an event we can use for caching
The text was updated successfully, but these errors were encountered: