Robot Languages - The Real Problem
This is a follow-up post to Robot Languages where the sorts of practical problems that robot developers have to face show up. There is an idea that's been going around for a while now called "Web Sockets". See the IETF specification RFC6455:
The WebSocket Protocol enables two-way communication between a client
running untrusted code in a controlled environment to a remote host
that has opted-in to communications from that code. The security
model used for this is the origin-based security model commonly used
by web browsers. The protocol consists of an opening handshake
followed by basic message framing, layered over TCP. The goal of
this technology is to provide a mechanism for browser-based
applications that need two-way communication with servers that does
not rely on opening multiple HTTP connections (e.g., using
XMLHttpRequest or <iframe>s and long polling).
The idea is that an HTTP 1.1 connection can be "extended" to allow it to act as a transport for another protocol, and in the case of web sockets, that other protocol is a sort of multiplexed virtual TCP/IP socket.
The libwebsockets project has written (https://github.com/warmcat/libwebsockets) 0.33 million lines of code --- that's 315,000 lines of C code + 10,000 of cmake and another 6,000 odd lines of C++, JavaScript and Bourne shell scripts --- to implement this API with additional layers to multiplex connections and add TLS/SSL. This now runs in every Android mobile phone. Welcome to SkyNet.
He didn't even have to press <enter>!
Subscribe to AlienOverlordz.
Britain's economic future is not technology, it's bullshit:
Subscribe to Declassified UK.
Bullshit that kills people by the millions:
Subscribe to Rachel Blevins.
All over the world:
Subscribe to Al Jazeera English.
Comments
Post a Comment