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
To support the QueryingSubscriber use cases described in #102, we require the possibility to declare a Publisher that will also maintain a local cache of its publications (at least 1 sample per path) and declare a queryable to return the content of this cache on queries.
The text was updated successfully, but these errors were encountered:
@JEnoch , I was thinking a bit more about this and there are a few use cases for which it would make sense to have a "storage" that behaves as a cache. We need to workout the details as there are some non-trivial points to be addressed when queurying a set of resources...
To support the QueryingSubscriber use cases described in #102, we require the possibility to declare a Publisher that will also maintain a local cache of its publications (at least 1 sample per path) and declare a queryable to return the content of this cache on queries.
The text was updated successfully, but these errors were encountered: