Hu: Every statement beyond the first layer of abstraction involves the inclusion of a conditional, which means that, the deeper your application goes, the greater the proportion of functions that will include a conditional. Conditionals provide interactivity to an application, as the user’s inputs will determine #, rather than the automated running of a script, the direction of control.
H3S1: Conditional str: lit-rev:<Turing>
H3S2: Conditional programming is categorically scalable<Turing>:
In conditional programming, the same small set of elements, as little as 6-8, will be remixed, ad infinite, and to varying depth, and these words are worthy of capitalization:
H4S1: History:
H5S1’s<fbno>: VOD | Files | Static | Content | Archive | HTTP | Half-duplex<WP.MIC-H2S66> | ; no matter how you name it, there is simply a type of thing, called History, and all such things, no matter how they manifest, need to manifest, in the same structure.
H4S2: Real-time:
H5S1’s: Streaming | Calling | Live | Synchronous | Responsiveness | Two-way | Updates | News | Automated | Fast Notifications | Persistent Connection | Full-duplex | Web-Sockets
H5S1: The history of real.time-web,dev:
Lengstorf, Leggetter<a-r>: One of the main problems with HTTP long-polling can be seen if there is a requirement for client/server bidirectional communication. Once the long-polling HTTP connection is open, the only way for the client to communicate with the server is to make another HTTP request. This can result in double the resources being used: one for server-to-client messages and another for client-to-server messages. The exact impact of this really depends on how much bidirectional communication is occurring; the more chatty the client and server are with each other, the greater the resource drain.
<pg-11> One of the most beneficial implications of widespread WebSocket support is in scalability: because WebSockets use a single TCP connection for communication between the server and client instead of multiple, separate HTTP requests, the overhead is dramatically reduced.
References:
Lengstorf, Jason, and Phil Leggetter. Realtime Web Apps: HTML, Websocket, PHP, and JQuery. Apress.