RFC 3205, On the Use of HTTP As a
Substrate,[56] has good design advice for anyone
considering using HTTP as the underlayer of an application
protocol, including a summary of the tradeoffs and problems involved.
About the only serious drawback of layering IPP over HTTP is
that the protocol is completely driven by client requests. Thus there
is no space in the model for printers to ship asynchronous alert
messages back to clients. (However, smarter clients could run a
trivial HTTP server to receive such alerts formatted as HTTP requests
from the printer.)
[an error occurred while processing this directive]