Hi WG, Updating transport mechanisms is an WG item and we are getting close to the milestone (in September). Hence, the authors are finalizing the updates as soon they can, and the topic will be a main item for the coming weekly meeting. It was suggested that we send out some main points for others to think about them before the meeting.
In particular, the goal is to finalize the version-dependent design, where by version independent, it means that the design can benefit from improvements in http without explicit control. Applying the inference, it means that the design should not use version specific methods, which will be PUSH_PROMISE. In other words, it should use only base http/1.x methods; that is, we use GET/PUT/POST. In this design space, there are still two design points: (D1): introducing PUT; (2) not introducing PUT. For discussion, we need to distinguish between ALTO server/client and HTTP server/client. In general design, an ALTO server can be an HTTP client and so on. For D1, to allow ALTO server pushing updates using PUT, the ALTO server needs to become an HTTP client. Hence, it needs two HTTP connections, with in one the ALTO server being an HTTP client and the other HTTP server. For D2, it needs only one HTTP connection, and the efficiency depends on low long-poll overhead in non-blocking HTTP/2/3. The authors prefer D2 and will finalize the document in a couple days. Any comments are greatly appreciated. Richard, Roland, Kai and Jensen -- Richard
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
