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.

Sign up for GitHub

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

Jump to bottom

Expiration enforcement #37

Open
kinlane opened this issue Jun 27, 2014 · 0 comments
Open

Expiration enforcement #37

kinlane opened this issue Jun 27, 2014 · 0 comments
Labels
question

Comments

@kinlane
Copy link
Contributor

kinlane commented Jun 27, 2014

3.4. Expiration

Robots may cache /apis.* files, but if they do they must
periodically verify the cached copy is fresh before using its
contents.

These look like they should be MAY and MUST. Why is it the robot’s responsibility to manage checking for refreshes, given that the metadata publisher is entirely in control of this parameter?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kinlane