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

store/provide remote metadata for Transfers #15

Closed
jdcasey opened this issue Jul 2, 2014 · 0 comments
Closed

store/provide remote metadata for Transfers #15

jdcasey opened this issue Jul 2, 2014 · 0 comments
Milestone

Comments

@jdcasey
Copy link
Member

jdcasey commented Jul 2, 2014

It would be very useful if galley would store metadata related to the retrieval of remote artifacts, then provide a mechanism in the Transfer class to read/query it.

For http connections, this would take the form of filing away the response status code/message, along with all of the response headers. It could be very useful in detecting content types, or diagnosing upstream connection problems...or even helping advise the not-found cache on whether to cache a missing artifact or not.

@jdcasey jdcasey modified the milestone: 1.0 Jun 11, 2015
@jdcasey jdcasey modified the milestones: 1.0, 0.9 Jul 29, 2015
@jdcasey jdcasey closed this as completed Jul 29, 2015
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

1 participant