Post-Rest
Stephen's Web ~ OLDaily, Nov 19, 2018

Tim Bray, Ongoing, Nov 19, 2018 REST stands for 'Representational State Transfer' and it was the nice light-weight way we created interfaces between programs running on the web (instead of using the heavy and over-engineered Web Services architecture). But now Tim Bray is looking at what comes after REST. "Mes­sag­ing and Event­ing... is all over, and I mean all over, the cloud in­fras­truc­ture that I work on," he writes. Request workflows are another area of focus. But the big changes are persistent connections and "QUIC (Quick UDP Inter­net Con­nec­tion­s) which aban­dons TCP in fa­vor of UDP, while re­tain­ing HTTP se­man­tic­s."  The idea is to speed up streaming content (such as games, messaging and video) as explained here. Web: [Direct Link] [This Post]
Tim Bray, Ongoing, Nov 19, 2018 REST stands for 'Representational State Transfer' and it was the nice light-weight way we created interfaces between programs running on the web (instead of using the heavy and over-engineered Web Services architecture). But now Tim Bray is looking at what comes after REST. "Mes­sag­ing and Event­ing... is all over, and I mean all over, the cloud in­fras­truc­ture that I work on," he writes. Request workflows are another area of focus. But the big changes are persistent connections and "QUIC (Quick UDP Inter­net Con­nec­tion­s) which aban­dons TCP in fa­vor of UDP, while re­tain­ing HTTP se­man­tic­s."  The idea is to speed up streaming content (such as games, messaging and video) as explained here. Web: [Direct Link] [This Post]