You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What would the recommended way to represent a read-only key-value store (populated from or fronting some other source) with these interfaces--have it export store but return errors from bucket.set and .delete calls? Is it worth considering having a read-only store interface, or is this use case too niche to warrant a separate interface?
The text was updated successfully, but these errors were encountered:
What will be the use cases for read-only key-value stores? Will wasi:runtime-config solve these use cases, which is a simply interface that provides read-only operations.
Yeah I'm definitely curious on the use case here. With the current interface, since it returns errors, you could create an implementation that returns an error on write ops. But I also understand you may want to have the interface indicate the difference
What would the recommended way to represent a read-only key-value store (populated from or fronting some other source) with these interfaces--have it export
store
but return errors frombucket.set
and.delete
calls? Is it worth considering having a read-onlystore
interface, or is this use case too niche to warrant a separate interface?The text was updated successfully, but these errors were encountered: