When assessing the two solutions, reviewers found OpenSSH easier to use and do business with overall. However, reviewers preferred the ease of set up with Apache HTTP Server Project, along with administration.
Ease of install and use, relatively easy to extend to enable critical web scripting langauges (php, perl, python), very flexible.
it is still too unstable when it comes to high concurrent connections, especially if such connections need to "talk" for a long time or handle a large amount of data with the PHP process manager integrated into Apache's LAMP stack, there is no possibility...
We have been using OpenSSH on our RedHat 6 and RedHat 7 servers for several years. I'm not sure if this is somethibng that comes default on Rackspace's Redhat servers or if they make it for us. Either way it generally just works. The thing I like most...
Example code wouldn’t connect to test ssh servers whereas putty did. This was enough to convince me the libraries would be more trouble than they’re worth.
Ease of install and use, relatively easy to extend to enable critical web scripting langauges (php, perl, python), very flexible.
We have been using OpenSSH on our RedHat 6 and RedHat 7 servers for several years. I'm not sure if this is somethibng that comes default on Rackspace's Redhat servers or if they make it for us. Either way it generally just works. The thing I like most...
it is still too unstable when it comes to high concurrent connections, especially if such connections need to "talk" for a long time or handle a large amount of data with the PHP process manager integrated into Apache's LAMP stack, there is no possibility...
Example code wouldn’t connect to test ssh servers whereas putty did. This was enough to convince me the libraries would be more trouble than they’re worth.