My proposed type of CGI would have an advantage (?) that it presents a bidirectional socket to the script, rather than a file that was already read and saved to disk and a write-only socket. CGI chat over a single http connection for example would be possible (if the browser/client also supported it).
Your CGI scripts aren't going to run on Plan 9 anyway. For the work it will take to port stuff you're better off inventing a better method that takes advantage of Plan 9's facilities.
I'm interested in what can be done on Plan 9, not on mythical utopias for other OSes intractable problems.
Ditch CGI, replace the execed scripts with long-running servers, and turn httpd into a dispatcher that hands off FDs based on a URL matching scheme. You could probably even hack up the plumber as the dispatcher.
--lyndon
