Talli ... a minor nit on the History Channel documentary you're scripting ...
NaviServer (AOLserver) was originally developed for Windows. That's why the old-style initialization files look just like Windows .ini files. They *were* originally.
As the people doing the native PG for Windows stuff have pointed out, multiprocessing programs for Windows are much easier to develop using threads rather than processes.
So going multithreaded on Windows wasn't really a stroke of genius, it's just the right way to do things in that environment.
Likewise in the Unix environment threading has been a PITA with everyone and his uncle inventing their own mode, while the multiprocessing model based on "fork()" has been around and standardized in Linux forever. Thus the decision by Apache and (long ago) PG developers to use processes not threads makes some sense, it reduces the maintenance effort.
Now ... every other decision made by Jim was truly brilliant and insightful :)
If CR were to write up a comparison of what it took to do what he describes in the Apache world vs. AOLserver world it would be a useful thing to shove at techies. Not IT managers, though.
