In this final installment of the series on Twisted, the author looks at specialized protocols and servers contained in the Twisted package, with a focus on secure connections. One thing the servers and clients in Parts 1,2 & 3 had in common is that they operated completely “in the clear”. Sometimes, however, you want to keep your connection free from prying eyes (or from tampering/spoofing).
although the author whines abit about it, he makes a good point about documentation. No matter how good a program is/could be, if it isn’t documented (or at least suffienctly internally documented and human readable within the source<–but that is still no replacement for good docs) it doesn’t really matter. I’d rather use something else altogether.
of course on the other end of the spectrum you have man pages documenting commands that have at least 50 different modifiers and it’s completly cryptic to read and understand.
e.g: $man screen