The same story is true on the client side. Any worthy Internet client
machine better have easy to use APIs to allow an app to talk HTTP
(Microsoft's OSes certainly offer that today). This means that your
programmers will again be happy hearing you guys have agreed upon an
HTTP based protocol since all they have to do is to use these rich APIs
to implement it (ask any programmer who codes Internet software for a
living).
Babak
>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
>