Are you suggesting that you'd like to see vendors have the ability
to implement *dynamic* binding of default job attributes rather than
the suggested *static* binding approach?
If this is what you are suggesting, what is the motivation?
----- Begin Included Message -----
From: Roger K Debry <rdebry at us.ibm.com>
To: <ipp at pwg.org>
Subject: Re: IPP> MOD - I've posted some issues: isstnh03.doc .pdf-Re
Date: Fri, 21 Mar 1997 09:58:18 -0500
Epilogue: Roger K deBry
Senior Techncial Staff Member
Architecture and Technology
IBM Printing Systems
email: rdebry at us.ibm.com
In answer to your question as to what happens if the Administrator
changes the Printer defaults after a job has been accepted (and defaulted):
There is no effect on the jobs that have already been accepted (and defaulted).
Only future jobs are affected with the new defaults. This is the simplest
to implement and for the end-user to understand. If the user queries his/her
job after it has been accepted and sees a value (that was defaulted), that
value will be the one that is used, even if the Administrator
subsequently changes the Printer's defaults.
RKD> Could this be implementation defined?
----- End Included Message -----