Jay,
I am very glad to see you summarizing the current situation like you
did. I certainly feel supported by you and Harald that a straight TCP
client-server model would be a better approach.
One comment I would like to make about people chanting the "Stock HTTP
Server" mantra:
"The Common Gateway Interface, or CGI, is a standard for external
gateway programs to interface with information servers such as HTTP
servers."
This is the definition to be found on the NCSA Web pages. And from all
the implementation suggestions, it sure sounds like HTTP is only going
to be used for hand-through to the "external gateway program". Not
much benefit in using the "Stock HTTP Server".
Babak from Microsoft has pretty much made the same point in his mail
from a couple of days ago.
-- Alex Bochannek Phone & Fax : +1 408 526 51 91 Senior Network Analyst Pager : +1 408 485 90 92 Engineering Services Alpha Pager : (800) 225-0256 PIN 104536 Cisco Systems, Inc. Email : abochannek@cisco.com 170 West Tasman Drive, Bldg. E Pager Email : abochannek@beeper.cisco.com San Jose, CA 95134-1706, USA