IPP Mail Archive: IPP> ADM - Minutes from the IPP Meeting in Toronto on August 19-20, 19

IPP Mail Archive: IPP> ADM - Minutes from the IPP Meeting in Toronto on August 19-20, 19

IPP> ADM - Minutes from the IPP Meeting in Toronto on August 19-20, 19

Carl Kugler (kugler@us.ibm.com)
Wed, 16 Sep 1998 16:29:51 -0600

This is a multi-part message in MIME format.
--------------4B4709B93DDD3E90510291B2
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by fwns1.raleigh.ibm.com id SAA29716

In reply to http://www.pwg.org/hypermail/ipp/1238.html=20

> Question The URI in the HTTP layer is either relative or absolute and i=
s used by the HTTP server to route the HTTP request to the correct resour=
ce relative to that HTTP server. This "resource" is either an IPP Printe=
r or a Job, right?
>=20
> The HTTP server need not be aware of the URI within the operation reque=
st. Once the HTTP server resource begins to process the HTTP request, it =
might get the reference to the appropriate IPP Printer object from either=
the HTTP URI (using to the context of the HTTP server for relative URLs)=
or from the URI within the operation request; the choice is up to the i=
mplementation.
>=20
> Once the Printer or Job ("the HTTP server resource") has begun to proce=
ss the job, why would it need a reference to an appropriate IPP Printer o=
bject?
>=20
> Implementation question: the server is REQUIRED to check for the prese=
nce of target URI operation attributes in every request (and respond with=
client-error-bad-request if not found) but is otherwise free to ignore t=
arget op. atts.? The Request-URI and target URLs might not be literally i=
dentical although they MUST both reference the same IPP object; however t=
he server isn't required to verify this?
>=20
> Carl Kugler

> Question 2 -- [Carl-Uno noted that the Discussion in the document is no=
t relevant to the Question. The Discussion will be removed, or atttached =
to a different Question (see below.)] Answer: Yes, the =93resource=94 is =
either an IPP Printer or a Job. However, the group was unable to address =
the remaining parts of the Question. They will request Carl Kugler to pro=
vide further clarification. It is (at least) unclear what assumptions are=
being made.

Okay, let me try to clarify.

We've established that the "HTTP server resource" referred to in the
document is either 1) an IPP Printer, or 2) an IPP Job. If we
substitute the words "IPP Printer (or IPP Job)" for "HTTP Server
resource" in the original sentence, we get:

> Once the IPP Printer (or IPP Job) begins to process the HTTP request, i=
t might get the reference to the appropriate IPP Printer object from eith=
er the HTTP URI (using to the context of the HTTP server for relative URL=
s) or from the URI within the operation request; the choice is up to the=
implementation.

I cannot understand this sentence. What are the words "appropriate IPP
Printer object" referring to in this sentence? Why would a Printer or
Job object processing an IPP request need a "reference to the
appropriate IPP Printer object"? What is the Printer or Job supposed to
do with the reference? =20

Note: I realize that the sentence in the document says "begins to
process the HTTP request", not "IPP request". However, if the "HTTP
server resource" processes only the HTTP part of the request (and not
the IPP), then there is no choice to use the URI within the IPP
operation request, so the sentence makes no sense.

-Carl
--------------4B4709B93DDD3E90510291B2
Content-Type: text/html; charset=us-ascii; name="1238.html"
Content-Disposition: inline; filename="1238.html"
Content-Base: "http://www.pwg.org/hypermail/ipp/1238.
html"
Content-Transfer-Encoding: 7bit

<!-- received="Mon Sep 14 17:26:19 1998 EDT" -->
<!-- sent="Mon, 14 Sep 1998 14:25:13 PDT" -->
<!-- name="Manros, Carl-Uno B" -->
<!-- email="cmanros@cp10.es.xerox.com" -->
<!-- subject="IPP&gt; ADM - Minutes from the IPP Meeting in Toronto on August 19-20, 19" -->
<!-- id="199809141958.AA16717@interlock2.lexmark.com" -->
<!-- inreplyto="" -->
<title>IPP Mail Archive: IPP&gt; ADM - Minutes from the IPP Meeting in Toronto on August 19-20, 19</title>
<h1>IPP&gt; ADM - Minutes from the IPP Meeting in Toronto on August 19-20, 19</h1>
Manros, Carl-Uno B (<i>cmanros@cp10.es.xerox.com</i>)<br>
<i>Mon, 14 Sep 1998 14:25:13 PDT</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#1238">[ date ]</a><a href="index.html#1238">[ thread ]</a><a href="subject.html#1238">[ subject ]</a><a href="author.html#1238">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="1239.html">Manros, Carl-Uno B: "IPP&gt; ADM - IPP Implementors' Guide Version 01"</a>
<li> <b>Previous message:</b> <a href="1237.html">Manros, Carl-Uno B: "IPP&gt; ADM - The crisis is over, we can go back to work"</a>
<!-- nextthread="start" -->
</ul>
<!-- body="start" -->
All,<br>
<p>
Here are the pointers to the minutes from Toronto:<br>
<p>
<a href="ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ipp-minutes-980819.doc">ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ipp-minutes-980819.doc</a><br>
<p>
<a href="ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ipp-minutes-980819.pdf">ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ipp-minutes-980819.pdf</a><br>
<p>
<a href="ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ipp-minutes-980819.txt">ftp://ftp.pwg.org/pub/pwg/ipp/minutes/ipp-minutes-980819.txt</a><br>
<p>
<p>
Thanks to Lee Farrell for taking the notes, which have been<br>
delayed in distribution due to the hick-ups with the DL. <br>
<p>
Carl-Uno<br>
<p>
Carl-Uno Manros<br>
Principal Engineer - Advanced Printing Standards - Xerox Corporation<br>
701 S. Aviation Blvd., El Segundo, CA, M/S: ESAE-231<br>
Phone +1-310-333 8273, Fax +1-310-333 5514<br>
Email: manros@cp10.es.xerox.com <br>
<!-- body="end" -->
<p>
<ul>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="1239.html">Manros, Carl-Uno B: "IPP&gt; ADM - IPP Implementors' Guide Version 01"</a>
<li> <b>Previous message:</b> <a href="1237.html">Manros, Carl-Uno B: "IPP&gt; ADM - The crisis is over, we can go back to work"</a>
<!-- nextthread="start" -->
</ul>

--------------4B4709B93DDD3E90510291B2--