Hi Linda,
Different clients can request different incremental updates and the load
balancing is applied to all requests. However, here the issue is mainly for a
single user whose requests may be distributed through different HTTP
connections (and eventually different TCP connections). The argument is that
some requests may arrive at a server that does not have the TIPS view if 1)
only one backend server hosts a specific TIPS view and 2) layer-4 load
balancing is used.
To eliminate the ambiguity, we propose the following text (to be included in
the next revision -17):
NEW:
TIPS allows a client to make concurrent pulls of incremental updates
for the same TIPS view potentially through different HTTP
connections. As a consequence, it introduces additional complexities
when the ALTO server is being load balanced. For example, a request
may be directed to a wrong backend server and get incorrectly
processed if the following two conditions both hold:
The server does not necessarily keep the state of each (client, TIPS view)
combination. It only manages states of the TIPS views (e.g., what incremental
updates are available, perf & usage statistics) and clients are responsible to
keep track of their states (e.g., which updates of a TIPS view they already
have).
Please let us know if that solves your problem. Thanks!
Best,
Kai
-----Original Messages-----
From:[email protected]
Send time:Thursday, 10/19/2023 01:22:25
To: "IETF ALTO ([email protected])" <[email protected]>,
"[email protected]"
<[email protected]>
Cc: "Linda Dunbar <[email protected]> ([email protected])"
<[email protected]>, gen-art <[email protected]>
Subject: fw Genart last call review of draft-ietf-alto-new-transport-15
Hi all,
It seems this review didn’t make it to the ALTO list:
https://mailarchive.ietf.org/arch/msg/gen-art/3q-ds8awHTaNIK4FRv1xTI_eqs8/
Cheers,
Med
____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou
falsifie. Merci.
This message and its attachments may contain confidential or privileged
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been
modified, changed or falsified.
Thank you.
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
