3 ms·

The architecture of the web (REST), always had intermediaries as first-class citizens. I can recommend reading into Fielding's dissertation! The declarative an

The architecture of the web (REST), always had intermediaries as first-class citizens. I can recommend reading into Fielding's dissertation! The declarative and stateless message design is partly motivated by the need for intermediaries processing and understanding the messages (ie POST must not be cached f.e.). I think the introduction explained it very well: The original design generalized too much for the needs of 2021 by putting all caches into a single bucket.

potamic 5y ago
It recognized the need for intermediaries sure, but I don't believe it treated them as first class citizens. The idea has always been to treat them as proxies. Proxies extend/enhance the behaviour of a certain process without changing the interfaces. This particular standard changes those interfaces by treating proxy communication different to target communication.
e12e 5y ago
The thesis: https://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm https://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm Of cache, see eg: https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm#fig_5_10 https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arc... > Layered system constraints 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. With REST (and without encryption or with trusted ssl stripping proxies) you can have a lan level cache - eg: if one of your 10 000 students access Fielding's thesis, that might be locally available for the potential 9 999 next requests. Typically this was useful for caching news site front pages - and could in theory work for video content too).

3 ms·

The architecture of the web (REST), always had intermediaries as first-class citizens. I can recommend reading into Fielding's dissertation! The declarative an

by wh33zle 5y ago

potamic 5y ago
It recognized the need for intermediaries sure, but I don't believe it treated them as first class citizens. The idea has always been to treat them as proxies. Proxies extend/enhance the behaviour of a certain process without changing the interfaces. This particular standard changes those interfaces by treating proxy communication different to target communication.
e12e 5y ago
The thesis: https://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm https://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm Of cache, see eg: https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm#fig_5_10 https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arc... > Layered system constraints 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. With REST (and without encryption or with trusted ssl stripping proxies) you can have a lan level cache - eg: if one of your 10 000 students access Fielding's thesis, that might be locally available for the potential 9 999 next requests. Typically this was useful for caching news site front pages - and could in theory work for video content too).