QUIC API Original Trial extended to support datagrams

The QUIC P2P API<https://w3c.github.io/webrtc-quic/> supports datagrams as well as reliable and unreliable streams - and now the Origin Trial has been extended, so that you can try it out for yourself.


The new datagram APIs will be available to registered origins in Chrome version 75, pushed to stable at the start of June 2019<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fappserve%2Fmkt%2Fp%2FAFnwnKUnUfkcpEMQ7rQhJtPx0N0QJ57wSja0lpPzXE3I-I-Ys_3PxZQIlugRDs80xWJ4gw2HonyvMLdPEAwkyHnVVjrB_SF6Uoo57Rg_kQ&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C18022dc947a44d163fc008d6d9823bcf%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636935550706635797&sdata=P1EPH0uMbe2%2BmsomCYWXDR%2BT9XgIK5Qq1RfQDS8gjHo%3D&reserved=0> (as well as Edgium Canary, soon afterward).

.


Sending

// Will resolve immediately if the transport is not

// congestion control blocked.

await quicTransport.readyToSendDatagram();

quicTransport.sendDatagram(newUint8Array([1,2,3]);


Receiving

// Will resolve immediately if the datagrams have been received & buffered,

// otherwise resolves when a datagram is received.

let datagrams = await quicTransport.receiveDatagrams();

for(let i =0; i < datagrams.length; i++){

 console.log(datagrams[i]);

}


More API information & examples can be found on the origin trial documentation github page<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fappserve%2Fmkt%2Fp%2FAFnwnKXwicUMuAa7SwGlP4_AVQnErNC14mqTlSexN7cI7Odo_Iuu0FsBJonEXHdIK5Eyl9bT_zQX-c8fCoNsQ1k_Otish_tNG8_5lIX965duWlJXOdJy6BCvOIKCs-bYFm6Z7jwdtQxyHAzMpw&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C18022dc947a44d163fc008d6d9823bcf%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636935550706640788&sdata=QtsuBz7dBcCY%2F8kyAeBdEu91euqjyY%2Fm3rIieGENxl8%3D&reserved=0>.


We really value your feedback in the origin trial and would appreciate your comments in the token renewal survey. If you have any questions do not hesitate to reach out to me.


Cheers,

Seth (shampson@chromium.org<mailto:shampson@chromium.org>)

Bernard (bernarda@microsoft.com)