Where did people get the notion that WebSockets have anything to do with REST or http?? websockets are a simple tcp connection, you know... like the one that CARRIES http!
So when people say stuff like this:
> First and foremost, how do you represent a URI? Second, how do you represent the HTTP methods (GET, PUT, POST, …)? A
How do we represent HTTP? Well, how about using HTTP ?!?!
(is everybody taking crazy pills, or am I missing some HUGE part of this discussion?)
"Last I checked, “bandwidth” is an infinite resource..."
No it is not. There has to be infrastructure to carry that bandwidth, so there is a very real and physical limit on bandwidth. Also, in many countries, bandwidth costs money. Downloading costs money. I know that in America it is easy to find unlimited internet plans (or close to it), but in many countries every gigabyte you downloads costs money. My limit is 40 gigabytes, for which I pay about 40 dollars. After that, every 10 gigabytes I download is an additional 6 dollars.
...and I'm pretty sure it was an ARM