-
Notifications
You must be signed in to change notification settings - Fork 16
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
Difference between ignoring and rejecting an update #131
Comments
Ah, that's an interesting distinction to draw attention to! Perhaps we should say more clearly that "a client can ignore the update, and a server can reject it." I wonder what status code the server should respond with? |
We also have longer-term plans to extend HTTP to allow clients to send acknowledgements back to servers. This might help with what you're doing. Note that this work is in Level 3 of the Protocol Roadmap— it requires moving HTTP beyond a request/response client/server architecture, and generalizing it into a P2P messaging system. (I presented on this in Braid Meeting 2. Here's a shortcut to the video explaining the relevant slides 12-15.) So whereas today's HTTP lets a client mutate a server (with acknowledgement):
And lets a server mutate a client (without acknowledgement):
We could generalize HTTP into a more symmetric, P2P future, like this:
This can generalize the I think this might help with what you're doing. Nobody has proposed a spec for it yet, but a compelling application could give us a reason to spec it up. |
The idea of reversing the roles of clients and servers was also brought up this fall at IETF 118 in @bemasc's Reverse HTTP proposal (slides). Austin Wright (@awwright) pointed out in that session that it's actually possible to do this today on HTTP, even though people don't. It wouldn't be supported in the browser |
I have a question;
So IIUC "ignore" applies to recipients that are http clients, and "reject" refers to recipients that are http servers?
Is this because the http server can send back a http status code but a client cannot?
The text was updated successfully, but these errors were encountered: