-
Enhancement
-
Resolution: Fixed
-
P3
-
1.4.0
-
None
-
beta
-
sparc
-
solaris_7
A public reviewer of the JPS API spec noted that the API does not
support a particular IPP attribute needed in his implementation.
"printer-uri" is sometimes needed to look up a printer based on a
globally unique identifier.
eg A customer is traveling and calls a colleague back home to get a
printed copy of a document on the home server. He tells the colleague
the URI of the Printer. The colleague prints the document to a
identified printer in the distant location via Java Print APIs.
He identifies the Printer by the URL he received.
Without the PrinterURI, this task is nearly impossible. Any set of
attributes (including PrinterName) would likely match hundreds of other
printers in the world. So PrinterURI (a globally unique name) is the
only reasonable mechanism to use.
support a particular IPP attribute needed in his implementation.
"printer-uri" is sometimes needed to look up a printer based on a
globally unique identifier.
eg A customer is traveling and calls a colleague back home to get a
printed copy of a document on the home server. He tells the colleague
the URI of the Printer. The colleague prints the document to a
identified printer in the distant location via Java Print APIs.
He identifies the Printer by the URL he received.
Without the PrinterURI, this task is nearly impossible. Any set of
attributes (including PrinterName) would likely match hundreds of other
printers in the world. So PrinterURI (a globally unique name) is the
only reasonable mechanism to use.