It doesn't except the W#C standards group assume this was all about web servers. Web sockets have two phases, phase on is to negotiate with HTTP to dump the HTTP protocol, the next phase is to execute the keep alive protocol, a small transaction protocol. Then you can send stuff in frame containers.
So a network of peer connected nodes are not a network of web servers, and doing the http setup accomplishes nothing. I use hsbb protocol, Hyper Simple Bunch of Bytes, mainly LazyJ ascii text. Hsbb wrk by ignoring the http part of websockets and going straight to the keep alive and framing protocols, both quite simple. I can keep the part of http concerned with passwords.
My current model does not match the industries past. Massive parallelism over the internet by bots never cares about html or gui or images, necessarily. It is all about bots talking to each other in a peer to peer network with plain text generated via the high speed join process.
Linux bloat, plow through it and much of it gets parsed out, unnecessary.
No comments:
Post a Comment