Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use custom media types for request and responses #96

Closed
stevvooe opened this issue Jan 22, 2015 · 1 comment
Closed

Use custom media types for request and responses #96

stevvooe opened this issue Jan 22, 2015 · 1 comment

Comments

@stevvooe
Copy link
Collaborator

Custom media types will make it easier for us to iterate on request and response formats for API methods. It will also make migrating to new formats and maintaining backward compatibility much more straightforward.

Implementation plan:

  1. Experiment with media types in webhook implementation Webhook notifications #42. For this, we'll try to use application/vnd.docker.distribution.events.v1+json for the event format.
  2. Set baseline use of application/json to refer to the current specification.
  3. Define custom media types for other formats (manifest, layers, etc.). Here are some possible examples:
    • Layer: application/vnd.docker.distribution.layer+tar
    • Manifest: application/vnd.docker.distribution.manifest.v1+json
    • Signed Manifest: application/vnd.docker.distribution.manifest.v1+prettyjws
@stevvooe stevvooe added this to the Registry/Future milestone Jan 22, 2015
@stevvooe stevvooe self-assigned this Jan 22, 2015
@stevvooe stevvooe added the Ready label Mar 10, 2015
@stevvooe stevvooe removed this from the Registry/Future milestone Mar 18, 2015
@stevvooe stevvooe removed the sprint label Jul 23, 2015
@dmcgowan
Copy link
Collaborator

Discussion now a part of OCI artifacts spec

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants