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
When working on upgrading pull command for ORAS CLI, I need to create a OCI store to avoid fetching duplicated blobs again and again from the remote source. I found the internal Proxy struct in ORAS-go's internal cas package is just what I need. Can we make the proxy struct public so clients can reuse it to build light-weight read-through caches?
Pros:
ORAS-go users can reuse the code to build caches in their software.
Cons:
The current implementation is only a read-through cache with no consistency guaranteed. If any blob is deleted on the origin storage side, the change won't be reflected in the proxy.
The text was updated successfully, but these errors were encountered:
When working on upgrading pull command for ORAS CLI, I need to create a OCI store to avoid fetching duplicated blobs again and again from the remote source. I found the internal Proxy struct in ORAS-go's internal cas package is just what I need. Can we make the proxy struct public so clients can reuse it to build light-weight read-through caches?
Pros:
ORAS-go users can reuse the code to build caches in their software.
Cons:
The current implementation is only a read-through cache with no consistency guaranteed. If any blob is deleted on the origin storage side, the change won't be reflected in the proxy.
The text was updated successfully, but these errors were encountered: