3 ms·
As cool as this is, it does seem to take the protocols-within-protocols trend to a farcical extreme. The stack for this is: Upgraded Phone System (As opposed t
by unimpressive 11y ago
As cool as this is, it does seem to take the protocols-within-protocols trend to a farcical extreme. The stack for this is:
Upgraded Phone System (As opposed to POTS.)
Internet Protocol
TCP/BSDSockets
WebSockets
WebAudio
A final layer so that you can emulate a POTS over WebAudio.
That's not really any fault of the authors, I'm just curious how many layers we're going to stack up before we start unwinding the coil for performance reasons.
- datashovel 11y agoOnce the javascript is loaded into the phone via web browser, my understanding is that the only steps left is direct connection to audio jack from the web page that is loaded into the browser. Certainly there are implications that this data (once generated by the browser) could be retransmitted over the web to some remote hardware, but it's not critical to get this to work.
- unimpressive 11y agoI hadn't considered that. Thanks for sharing. :)
- jlgaddis 11y agoThe networking industry likes to do this too. For example, VXLAN: > "It uses a VLAN-like encapsulation technique to encapsulate MAC-based OSI layer 2 Ethernet frames within layer 4 UDP packets, ..." -- https://en.wikipedia.org/wiki/Virtual_Extensible_LAN Before that, MPLS: IPv6-in-IPv4 over PPPoE over HDLC over MPLS over an Ethernet VLAN inside a service provider's VLAN (Q-in-Q) over MPLS CSC to another ISP halfway across the country to ...
- icebraining 11y agoWebSockets are not that much of a protocol, after the handshake all it does is provide message framing.