I'm curious - why is Telnet "a fact of history"? It seems to work fine for most of us. 73, Pete N4ZR Check out the Reverse Beacon Network at <http://reversebeacon.net>, now spotting RTTY activity wo
Because more and more ISPs, firewalls, companies, etc are blocking telnet due to security concerns, especially with IOT and industrial devices which still use it instead of SSH. So the end user (like
TCP is a transport-layer protocol, and HTTP is an application-layer protocol that runs over TCP. Just like Telnet. If you worried about ports, couldn't you run Telnet on port 80 and be done with it?
Apart from the security issues (meaning it is blocked by firewalls) as Sterling had mentioned, HTTP is far easier to integrate into modern applications. Telnet also requires you to open a session and
There are networks that seem to block by traffic by protocol in addition to blocking by port or destination. I do wonder about how realistic an HTTPS-based cluster protocol (plain ol' HTTP isn't quit
it's easy to stream data via http(s). The server simply keeps sending data and the client will read as long as new data arrives. I implemented a web cluster with this years ago. But it's even nicer t