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

RFC7234: "disconnected" #5

Closed
mnot opened this Issue Apr 29, 2015 · 2 comments

Comments

Projects
None yet
1 participant
@mnot
Copy link
Member

mnot commented Apr 29, 2015

Caching still refers to a "disconnected" state, as well as "cannot reach" and similar states. This needs to be rationalised.

See thread:
http://www.w3.org/mid/CAAvUidMuV=e_yQZQjbqTr42afyvv1-5ambwBT5EcFL18juauWQ@mail.gmail.com

@mnot

This comment has been minimized.

Copy link
Member Author

mnot commented Oct 9, 2018

Should wait for resolution of #139.

@mnot

This comment has been minimized.

Copy link
Member Author

mnot commented Nov 13, 2018

I'm inclined to move the definition of "disconnected" up into "overview of cache operation" and refer to it consistently -- including when "cannot be reached" is used.

@mnot mnot added the has-proposal label Nov 29, 2018

@mnot mnot closed this in d86e194 Dec 2, 2018

reschke added a commit that referenced this issue Dec 2, 2018

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