[alto] ALTO transport discussion thread

"Y. Richard Yang" <yry@cs.yale.edu> Tue, 01 March 2022 04:38 UTC

MIME-Version: 1.0
From: "Y. Richard Yang" <yry@cs.yale.edu>
Date: Mon, 28 Feb 2022 23:38:24 -0500
Message-ID: <CANUuoLrr1-r60KiXHCPRMu1SukcdRay8ZE7_2NA1aURG-DumQA@mail.gmail.com>
To: IETF ALTO <alto@ietf.org>, Roland.Schott@telekom.de
Content-Type: multipart/alternative; boundary="000000000000ed7cd605d920bcd9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/uce_e9fQAKn_Jdr_pNVrFfPsS_0>
Subject: [alto] ALTO transport discussion thread
Precedence: list

Hi ALTOers,

Several of us (Roland, Kai, me) are working on ALTO transport, and our plan
is to update a relatively complete version by the draft deadline of March 7
(one week from today).

Here is a brief summary of current design points:
- It will be RESTful, as the current design
- It will redesign ALTO SSE functions by introducing update queues so that
(1) the server can organize incremental updates into the queues; (2) the
server can push updates to the client using the queue URI (to be consistent
with HTTP/2 PUSH_PROMISE semantics); and (3) the client can request content.

The main remaining issue that we will finalize is how to allow clients to
rejoin, and we will finalize the initial design soon. All are welcome to
join to work together.

Thanks,
Richard and Roland

[alto] ALTO transport discussion thread Y. Richard Yang