>Roy, would implementing it as a Java servlet be braindead?
That depends on the servlet API.
>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. 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.