IPP Mail Archive: Re[2]: IPP>MOD - Print by reference

Re[2]: IPP>MOD - Print by reference

Bill Wagner (bwagner@digprod.com)
Wed, 11 Jun 1997 13:00:44 -0400

Don,

I certainly agree that the approach should be pursued, although
perhaps the actual division might be somewhat different. Indeed, as I
may have inadequately indicated before, I thought Carl-Uno had
suggested that something like this may be necessary a long time ago.

The key, and perhaps the difficult part, is to ensure that the various
related but independently specified IPP services, are compatible with
each other so that a device could support all services in a cohesive
way.

Bill Wagner, Osicom/DPI

______________________________ Reply Separator _________________________________
Subject: Re: IPP>MOD - Print by reference
Author: don@lexmark.com at Internet
Date: 6/11/97 10:03 AM

I have been listening to this discussion for a long time and I recognize
the
need for a human being to be able to print by reference. This function can
be easily provided with HTML, etc on a Web page hosted by an IPP print
server (actually IPP is not even needed for this solution.) Is the need as
pressing for this to be done programmatically? The bottom line is can this
function be provided outside the scope of the IPP protocol? If the
programmatic need is strong, is it sufficient to standardize the way this
is
done with HTML so that once the URL of a print by reference page is
know, a print by reference job can be submitted to it under program
control?

This could just be part of a multi-pronged standard approach. Instead of
defining an all encompassing IPP standard, maybe we should
look at this from a difference perspective. Do we really need:

1) An IPP Job Submission protocol
-and-
2) An IPP Print by Reference standard
-and-
3) An IPP Job Management protocol
-and-
4) An IPP Print Capability Discovery protocol
etc, etc, etc.

I know "compliance levels" and print by reference are not strictly related
but I would like to be able to define all these functions in a standard
way without requiring "compliance levels" or burdening the lowest
implementation with too much baggage.

... all right... fire away!!

Don