2 ms·
"I hear the excuse, "it uses too much CPU time", but this is often from people who have written their web applications in Ruby" I'm curious about this, are the
by look_lookatme 17y ago
"I hear the excuse, "it uses too much CPU time", but this is often from people who have written their web applications in Ruby"
I'm curious about this, are these excuses you've heard based on configurations where a proxy server processes the initial https req and then sends the backend request encrypted, too? This is where Ruby is handling an encrypted request?
Or are you saying there are people who have excused https from their setup because their frontend web server is written in Ruby?
- jon_dahl 17y agoThe poster's point isn't really about Ruby. Ruby works just fine with HTTPS, thank you very much. It's not like Ruby handles the HTTPS encryption. I think his point is more "I hear the excuse 'it uses too much CPU time', but this is often from people who [should be looking elsewhere if they have performance problems]".
- look_lookatme 17y agoAh I see. I was confused. It didn't occur to me that he or she uses Ruby (in italics) as a catch all for slow application performance, not slow encryption performance. That said, do people really eschew https because they are that CPU strapped? Bizarre.
- jrockway 17y agoExactly; thanks for clarifying. :)