IPP> Implementers guide and table1

IPP> Implementers guide and table1

IPP> Implementers guide and table1

henrik.holst at i-data.com henrik.holst at i-data.com
Fri Sep 3 03:15:15 EDT 1999


You are right. Then I don't understand why we have the 'Summary of Operation
Attributes' (table 1)
in the IIG.

Holst





kugler at us.ibm.com on 02-09-99 20:25:59

To:   ipp at pwg.org
cc:    (bcc: Henrik Holst/INT)

Subject:  Re: IPP> Implementers guide and table1




If I'm not mistaken, those tables already exist in section 3.1.2.1.4.3,
 "Validate the presence of a single occurrence of required Operation
attributes".

    -Carl

kugle- at us.ibm.com wrote:
original article:http://www.egroups.com/group/ipp/?start=6295
>
> What I mean is, that the table 1 we have in the IIG, explains what
the IPP
> Client MUST and SHOULD
> send to the IPP Printer. But I think that we need a table telling
what the IPP
> Printer MUST and SHOULD
> send to the IPP Client, and also two other tables describing what
both the IPP
> Client and the
> IPP Printer MUST and SHOULD support of operations and attributes.
>
> E.g.:
> The IPP Client SHOULD send the 'requesting-user-name' attribute in a
'Print-Job'
> operation, but the IPP Printer MUST support it.
>
> Holst
>
>
>
>
>
> Ira Mcdonald <imcdonal at sdsp.mc.xerox.com> on 31-08-99 16:36:09
>
> To:   Henrik Holst/INT, ipp at pwg.org
> cc:
>
> Subject:  Re:  IPP> Implementers guide and table1
>
>
>
>
> Hi Henrik,
>
> Do you mean what the receiver (IPP Client) of a request MUST send
> in a response?  What do you envision in this table?  I'm in
> favor of tables when they can help, just curious.
>
> Cheers,
> - Ira McDonald
>
>
>
>
>








More information about the Ipp mailing list