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
We should allow the registry preference header (Julia-Registry-Preference) to not just be a single value, but a comma-separated list. The Pkg server should attempt to serve each registry flavor, in order. The client can use the meta-flavor default to allow the PkgServer to make an informed decision, and if none of the choices can be found, /registries should return 404. If the header is missing, it is assumed to be equal to default, thereby maintaining the current behavior.
Let us imagine that this is a hypothetical Julia v2.3 client, which knows about the existence of the super-conservative flavor, but allows fallback to the conservative flavor if the server doesn't serve the former. In this scenario, if the server does not serve either kind, it should return a 404.
This will select the eager flavor first, if it exists, and if it doesn't it chooses conservative, then finally falling back to whatever flavor the PkgServer thinks is best. This is a convenient way to future-proof clients against naming changes.
The text was updated successfully, but these errors were encountered:
We should allow the registry preference header (
Julia-Registry-Preference
) to not just be a single value, but a comma-separated list. The Pkg server should attempt to serve each registry flavor, in order. The client can use the meta-flavordefault
to allow the PkgServer to make an informed decision, and if none of the choices can be found,/registries
should return 404. If the header is missing, it is assumed to be equal todefault
, thereby maintaining the current behavior.Examples:
Let us imagine that this is a hypothetical Julia v2.3 client, which knows about the existence of the
super-conservative
flavor, but allows fallback to theconservative
flavor if the server doesn't serve the former. In this scenario, if the server does not serve either kind, it should return a 404.This will select the
eager
flavor first, if it exists, and if it doesn't it choosesconservative
, then finally falling back to whatever flavor the PkgServer thinks is best. This is a convenient way to future-proof clients against naming changes.The text was updated successfully, but these errors were encountered: