|
|
|
|
|
by geezerjay
2899 days ago
|
|
> If you control the client, then there's absolutely no reason to use HTTP: What about ensuring that your desired ports are opened and your connection won't be eaten by a random firewall because you happened to pick a closed port and the user doesn't want to be bothered with firewalls and your application suddenly is crap because it can't even get its network connection to work when every other alternative works out of the box? |
|
That's not a problem home-users have: They NAT.
Meanwhile in the enterprise, 80/443 is frequently locked into a particular (cheap) HTTP proxy server that can't manage basic features of HTTP correctly.