Hello Dhaya, this talk use the Presentation API ;)
First video is 10`, second is 50`
HTTP 2 & HTTP 3 are low layers optimizations for huge performance boost, without large impact or breaking changes to application layers.
We'll see why those simple constraints matters. I Won't talk about "Client–server", it's pretty obvious, nor about "Code on demand". Let's keep "Uniform interface" for later.
Enables intermediate processing by constraining messages to be self-descriptive: interaction is stateless between requests, standard methods and media types are used to indicate semantics and exchange information, and responses explicitly indicate cacheability.
Allow intermediaries—proxies, gateways, and firewalls—to be introduced at various points in the communication without changing the interfaces between components, thus allowing them to assist in communication translation or improve performance via large-scale, shared caching.
- modifiability of components to meet changing needs (even while the application is running) - visibility of communication between components by service agents - portability of components by moving program code with the data - reliability in the resistance to failure at the system level in the presence of failures within components, connectors, or data
A model, developed by Leonard Richardson, that breaks down the principal elements of a REST approach into three steps. These introduce resources, http verbs, and hypermedia controls.
Take a mental (or actual) picture
🅱️
🅰️
🅱️
🅱️
🆎
It's my last R&Day talk :/ See you @ Open R&Day