distribution/registry
Stephen J Day 69e477f2d5 Use done channel to avoid goroutine leak
This deals with a memory leak, caused by goroutines, experienced when using the
s3 driver. Unfortunately, this section of the code leaks goroutines like a
sieve. There is probably some refactoring that could be done to avoid this but
instead, we have a done channel that will cause waiting goroutines to exit.

Signed-off-by: Stephen J Day <stephen.day@docker.com>
2015-04-28 14:40:20 -07:00
..
api/v2 Updated urlbuilder X-Forwarded-Host logic 2015-04-24 14:16:49 -07:00
auth fix some typos in source comments 2015-04-17 12:39:52 +00:00
client Remove unnecessary close in client 2015-03-03 19:29:12 -08:00
handlers Add configuration for upload purging 2015-04-27 11:06:15 -07:00
middleware Rename top level registry interface to namespace 2015-04-09 19:21:33 -07:00
storage Use done channel to avoid goroutine leak 2015-04-28 14:40:20 -07:00
doc.go Integrate layer info cache with registry and storage 2015-04-02 20:15:16 -07:00