Stephen Day

@adamjaso The source document is https://github.com/docker/distribution/blob/master/docs/spec/auth/scope.md. If you don't mind sending a PR with the changes you want, we can work to make sure that its covered. If not, we'll...

@dnephin Please do. I wish this was a precursor to shutting down engine-api project. In general, the client available in `docker/docker` should represent the forward/backwards compatibility horizon of the docker...

> @ibuildthecloud Ignore the black magic required to do trusted pulls, just parsing a string to ImageID and Tag is not even straight forward. I noticed this yesterday while looking...

@vdemeester It may also make sense in distribution.

This should be hidden behind the Go API. One should not be deserializing a raw `io.ReadCloser`. The signature should be something like: ``` ImagePull(ctx context.Context, name string, opts ImagePullOptions) (Progress,...

I have a helper function with the following signature in my local project using an api similar to this (events): ``` go (*client).Events(ctx context.Context, options types.EventOptions) (messages

@calavera I'm going to wire this up nearly identically in my current project, and then come back with a PR if it works out.

@tamird #315 is the closest to providing progress here. If someone wants to take on the design from https://github.com/docker/engine-api/issues/89#issuecomment-198570221, that would be great, but I can probably get to this...

This looks good. The only question I have is about error handling: do we want a way to have the listener detect the error on write?

@yangguoyk2015 This package is a generic event distribution package. So the answer is yes. Is there specific code to do exactly this within this package? No. Please read the documentation...