3 ms·
I'm speaking abstractly, not literally. HTTP is still the destination for anything sent from the server (unless you're using SPDY), but that's literally. Abstra
by bradleyland 15y ago
I'm speaking abstractly, not literally. HTTP is still the destination for anything sent from the server (unless you're using SPDY), but that's literally. Abstractly, I'm referring to the fact that we used to build web apps that output HTML web pages, which were streamed over HTTP. The "application" was entirely on the server. The browser was, in effect, a dumb terminal. Nothing "interesting" was happening on the browser. Heh, tell that to the early browser developers :)
When you get down in to the details, it all seems so obvious, but that's kind of the point. Step back and stop thinking about how all this stuff happens. Sometimes, a detailed understanding is a hindrance. There's a saying, "can't see the forest for the trees," that applies very well here. Step back, ignore the details for a moment, and look at things broadly.
- jamesbritt 15y agoAbstractly, I'm referring to the fact that we used to build web apps that output HTML web pages, which were streamed over HTTP. The "application" was entirely on the server. The browser was, in effect, a dumb terminal. Then 1999 happened and we got true Web apps (smarts in the browser fetching data from the server) as well as the mixed-bag of XML-RPC and HTTP as a post-Web-page transport[0]. Not that I don't think that Apple is seeing the Internet as that thing that connect Apple products, just that this is not a rare or recent concept. [0] Or earlier, depending on your view of Java applets.