- From: Bin Ni <nibin@quantil.com>
- Date: Thu, 1 Aug 2019 01:49:58 -0700
- To: Daniel Stenberg <daniel@haxx.se>
- Cc: Jack Firth <jackhfirth@gmail.com>, Chris Lemmons <alficles@gmail.com>, Amos Jeffries <squid3@treenet.co.nz>, HTTP Working Group <ietf-http-wg@w3.org>
- Message-ID: <CAFifEML6zwvKZJwO0P0L_bvOq8ow1U1j4UkfOTJf0CDRjL71ig@mail.gmail.com>
Let me try to explain my proposal with some human language :) 1. the "Alt-Svc" behavior: Client: Hi Server-1.1.1.1, can you send me the movie XXX? Server-1.1.1.1: Here is the movie, but next time, you'd better ask server 2.2.2.2 for this movie. (It then took 2 hours to deliver the movie) 2. my proposed behavior: Client: Hi Server-1.1.1.1, can you send me the movie XXX? Server-1.1.1.1: Sorry, I can't give you the movie, you need to ask server 2.2.2.2 for this movie. Client: Hi Server-2.2.2.2, can you send me the movie XXX? Server-2.2.2.2: Here is the movie. (It then took 0.5 hours to deliver the movie, because server-2.2.2.2 is closer to the client, or less loaded) Bin On Thu, Aug 1, 2019 at 12:56 AM Daniel Stenberg <daniel@haxx.se> wrote: > On Thu, 1 Aug 2019, Jack Firth wrote: > > > Yes you could make a status code, but I don't follow why you need a new > > status code instead of reusing a generic 300 response with body > explaining > > they need to follow Alt-Svc. A special status code requires clients to > > implement new behavior, and if they're doing that already can't they just > > implement Alt-Svc support instead? > > No, because Bin wants to (as I understand it) force the next request that > uses > that origin to *forcibly* use the new alternative IP address. I'm pretty > sure > most alt-svc implementations will not do that but will rather reuse > existing > connections (since the spec allows that and it is much faster) and then > switch > to the alternative only once a connection to that has been setup... > > -- > > / daniel.haxx.se > -- Bin Ni VP of Engineering [image: Quantil] Connecting users with content...it's that simple. Office: +1-888-847-9851 <(888)%20847-9851> [image: Tweeter] <https://twitter.com/Team_Quantil> [image: Google Plus] <https://plus.google.com/+Quantil_team/> [image: Linked In] <https://www.linkedin.com/company/quantil> The information contained in this email may be confidential and/or legally privileged. It has been sent for the sole use of the intended recipient(s). If the reader of this message is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please reply to the sender and destroy all copies of the message. To contact us directly, send to QUANTIL, INC. at 1919 S Bascom Ave #600, Campbell, CA 95008 <https://maps.google.com/?q=1919+S+Bascom+Ave+%23600,+Campbell,+CA+95008&entry=gmail&source=g>, or visit our website at www.quantil.com. <https://www.quantil.com/>
Received on Thursday, 1 August 2019 08:50:36 UTC