The TAPS Architecture for Transport Services provides a framework for the design of a protocol-independent asynchronous message-based transport API. While the traditional BSD socket API requires the user to make a choice about which protocol to use from the beginning, the TAPS API focuses on transport features and gives the transport stack itself the opportunity to select the most appropriate protocol. This flexibility also supports deployment of new protocols, such as QUIC, because the application does not need to change in order to benefit from such new innovations. This poster defines two API mappings for QUIC, either exposing multistreaming explicitly to the application or providing a way to utilize multistreaming without application input.
|Publication status||Published - 4 Dec 2018|
|Event||CoNEXT Workshop on the Evolution, Performance, and Interoperability of QUIC - Heraklion, Crete, Greece|
Duration: 4 Dec 2018 → 4 Dec 2018
|Conference||CoNEXT Workshop on the Evolution, Performance, and Interoperability of QUIC|
|Abbreviated title||ACM COnEXT EPIQ|
|Period||4/12/18 → 4/12/18|