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

Hour of the Dead #2

Open
ptbrown opened this issue Mar 15, 2015 · 2 comments
Open

Hour of the Dead #2

ptbrown opened this issue Mar 15, 2015 · 2 comments
Labels

Comments

@ptbrown
Copy link
Contributor

ptbrown commented Mar 15, 2015

Should there be an HotD? A time (UTC) during which no clacks messages may be sent.

@madbobmcjim
Copy link
Contributor

Yeah definitely :-)

I don't think the protocol should be enforcing an HotD, but as it's an interconnection into or out of a Clacks network, and different Clacks networks might be running different HotDs, maybe a HotD-delivery-failed header response and the User-Agent should try again later? Or allow for buffering the requests at the edge of the network to be transmitted post HotD (with appropriate HotD-delivery-delayed response header)

@ptbrown
Copy link
Contributor Author

ptbrown commented Mar 19, 2015

503 Service Unavailable. This looks like the correct response. As you say each external network will have its own HotD. We can say that conforming CoHTTP gateways SHOULD send Retry-After but they're still allowed to refuse connections.

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

No branches or pull requests

2 participants