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 serving container requests Wave behave as a proxy in between the Docker client and the target container registry.
This means that to serve requests it's needed to connect the target registry, and therefore the quality of the service may be affected by the reliability of the target registry.
To improve the service throughput all redirect responses from the target registry can be cached by wave to avoid to avoid reaching the remote service once the response has been collected.
This goal can be achieved caching the result of handleRequest, when:
When serving container requests Wave behave as a proxy in between the Docker client and the target container registry.
This means that to serve requests it's needed to connect the target registry, and therefore the quality of the service may be affected by the reliability of the target registry.
To improve the service throughput all redirect responses from the target registry can be cached by wave to avoid to avoid reaching the remote service once the response has been collected.
This goal can be achieved caching the result of handleRequest, when:
The text was updated successfully, but these errors were encountered: