Encrypted communication on amateur radio bands is prohibited by law in the US, so transmitting an encrypted signal just invites spooks to triangulate your transmitter's position.
My son used to play a silly little match game that he picked up from pre-school when he was three years old. In it, he would take two toys -- cars, action figures, Lego blocks, staple removers, whatever -- hold them in his hands, and ask "Which one are you, X or Y?" After the other person (usually me) answered, he'd act out some sort of epic battle between the two toys in his hands, and then declare one or the other the victor. I always pointed out to him the pointlessness of the game. He didn't care.
Jeff Cogswell's reviews remind me of that game. They're pointless. He doesn't care. And my son grew out of it.
Slashdotters don't have sex, and so they cannot have slashdaughters. Ergo, slashdaughters do not exist. QED.
If you're going for speed, you'd be better off serving the HTTP direct from Tomcat and cutting Apache or IIS out of the loop entirely.
Tc-native supports HTTP, HTTPS, and AJP, so you still get native code to handle your sockets whether you want to put a separate HTTP in front of Tomcat or not. The Java-based connectors might be fast, but the native connectors are even faster.
The official Tomcat installer for Windows (as in, the one that you'd download from tomcat.apache.org installs the Tomcat Native Connector, which improves performance considerably. And there's a lot of vertical market applications for Windows that bundle Tomcat.
The seven-layer cake is a lie.