>
> >Should every
> >application that uses HTTP as a transport build in its own HTTP
> >implementation, even if one is already available on the platform?
>
> No application should use HTTP as a transport.
I don't think everyone would agree with that statement. See
Network Working Group Keith Moore
Internet-Draft University of Tennessee
5 August 1998 Patrik Faltstrom
Expires: 5 February 1999 Tele2
On the use of HTTP as a Substrate for Other Protocols
draft-iesg-using-http-00.txt
> If it used HTTP as HTTP,
> there wouldn't be any need for a separate implementation, but it would
> still be desirable to base the service on the best capabilities of HTTP
> and not on the characteristics that might be true of some other resources
> that are accessible via HTTP.
>
> ....Roy
>