Keith Moore wrote:
>> If nothing else, printing protocols and the web each need to evolve
> separately; we need to be very careful about how we tie them together.
I think we need to decide whether or not we are doing IPP or WPP
(Internet Printing Protocol or Web Printing Protocol)
The statement made by Keith (included in this msg above) I think is
crucial. I haven't thought about the ramifications (and permutations)
of tying a printing protocol to another N-numbered set of technologies
like HTTP, LDAP, CGI, and HTML (if we decide to use forms). It looks
like it might be more than we want to get into, at least from an
interoperability and maintenance standpoint.
At any rate, we need to think about someone that wants to do
printing across the internet, but does not want to be burdened with
the cost of implementing HTTP (or even HTTP-lite).
In this same vein, it would be very difficult to account for IPP
usage if we "hide" the IPP protocol within a set of HTTP accesses,
using the HTTP TCP port number, for example. This echoes the
ideas expressed by Alex earlier, and would also allow net-admins to
create policies that enable/disable HTTP and/or printing as
separate applications, something that sounds desirable IMHO.
(Good luck sorting this out in New Mexico ;)
Sharp Laboratories of America
rturner at sharplabs.com