slicehost wasn't shuttered so much as rebranded. rackspace didn't have a viable vm service prior to slicehost.
rackspace never had a "shared hosting" product outside of a very short lived acquisition of mosso from like 2007-2008....
how do you block websockets in a world with tls around the majority of http connections? wouldn't you have to resort to proxies with certificate authorities forced on users in order to block websockets?
slicehost wasn't shuttered so much as rebranded. rackspace didn't have a viable vm service prior to slicehost.
rackspace never had a "shared hosting" product outside of a very short lived acquisition of mosso from like 2007-2008....
how do you block websockets in a world with tls around the majority of http connections? wouldn't you have to resort to proxies with certificate authorities forced on users in order to block websockets?