Stephen J Day f536633ca8 spec: fetch manifests by tag or digest ... Manifests are now fetched by a field called "reference", which may be a tag or a digest. When using digests to reference a manifest, the data is immutable. The routes and specification have been updated to allow this. There are a few caveats to this approach: 1. It may be problematic to rely on data format to differentiate between a tag and a digest. Currently, they are disjoint but there may modifications on either side that break this guarantee. 2. The caching characteristics of returned content are very different for digest versus tag-based references. Digest urls can be cached forever while tag urls cannot. Both of these are minimal caveats that we can live with in the future. Signed-off-by: Stephen J Day <stephen.day@docker.com>		2015-03-04 21:39:36 -08:00
..
descriptors.go	spec: fetch manifests by tag or digest	2015-03-04 21:39:36 -08:00
doc.go	Move registry api definitions under registry package	2015-02-10 17:32:22 -08:00
errors.go	spec: fetch manifests by tag or digest	2015-03-04 21:39:36 -08:00
errors_test.go	Move registry api definitions under registry package	2015-02-10 17:32:22 -08:00
names.go	documentation for name validation grammar	2015-03-02 10:55:31 -08:00
names_test.go	Move registry api definitions under registry package	2015-02-10 17:32:22 -08:00
routes.go	Path prefix support for running registry somewhere other than root of server	2015-02-26 16:04:43 -08:00
routes_test.go	spec: fetch manifests by tag or digest	2015-03-04 21:39:36 -08:00
urls.go	spec: fetch manifests by tag or digest	2015-03-04 21:39:36 -08:00
urls_test.go	Path prefix support for running registry somewhere other than root of server	2015-02-26 16:04:43 -08:00