I don't think there is a real need to make the browsers IPP-aware. I
would much prefer the OS (i.e. the priting subsystem) to be IPP-aware
instead, where the browser can be treated as just another application.
When it comes to view the printer status, etc., the browser does not
have to talk a new protocol, rather HTTP/HTML should be all that is
needed.
Babak
>-----Original Message-----
>From: Tom Hastings [SMTP:hastings at cp10.es.xerox.com]
>Sent: Monday, March 03, 1997 9:19 AM
>To: rdebry at us.ibm.com>Cc: ipp at pwg.org; don at lexmark.com>Subject: IPP> Re: REQ - ISSUE - Dependencies on browsers
>>I think we all agree that the requirements document should be
>changed to not be called "Requirements for WEB-based broswer
>Internet Printing". We certainly want IPP to be used from any
>application on the desktop (transparently to the application and
>to the desktop printer driver).
>>However, browsers are updated on a frequent basis and made available
>either free or for a low price, so that one way to deploy a new protocol
>is for the browsers to pick up the new protocol. That may be why
>some in the IPP have been advocating a protocol similar to HTTP, but
>not actually the same. Because if IPP is similar, then it will be easier
>for the browsers to be updated. If IPP is not the same as HTTP, then
>some of the baggage that will go along with HTTP as it evolves will not
>need to be dragged along into IPP. Those of us who have been advocating
>to use HTTP directly have been trying to solve the deployment problem
>by being able to use existing browsers.
>>So we need some kind of requirement that says whether IPP is depending
>on using existing browsers, or can wait for the next round of browser
>deployments.
>>The other way that IPP will be deployed is for the "port drivers", also
>called re-directors, that sit under the desktop printer driver and relays
>to the remote printer what the desktop printer driver thinks is control
>and data that the desktop printer is sending to the local printer.
>>Is there some kind of requirement or assumption that we can agree upon
>and add to the requirements that would be something like "Assumed
>Deployment Strategy and Timing"?
>>Tom
>>>At 10:43 02/27/97 PST, rdebry at us.ibm.com wrote:
>>Classification:
>>Prologue:
>>Epilogue: Roger K deBry
>>Senior Techncial Staff Member
>>Architecture and Technology
>>IBM Printing Systems
>>email: rdebry at us.ibm.com>>phone: 1-303-924-4080
>>>>Don, I gave the requirements document a quick read. The major
>>comment I have is that the way the document is currently written,
>>it would appear that the only required client interface is a Web
>>Browser. While I would agree that using a Web Browser is an
>>important requirement, the document should not lead one to
>>believe that it is the only requirement! Since the first paragraph
>>in the Terminology section discusses the use of Worl Wide Web
>>tools, and Browsers are explicitly dicsussed in the second paragraph,
>>there is no need to explicitly call out Browsers (and not mention other
>>kinds of clients) in each of the remaining sections.
>>>>For example:
>>>>Change the title to "Requirements for An Internet Printing Protocol"
>>>>In the abstract chnage the first sentence to read "This document
>>describes the requirement for An Intrenet printing protocol."
>>>>In section 2, REQUIREMENTS, change the first sentence to read
>>"The next three scetions identify the requirements of an Internet
>>printing protocol ..."
>>>>In section 2.1.3, Viewing the status of a printer, chnage the first
>>sentence to read "Before using a selected printer or, in fact at
>>any time, the end user needs the ability to verify the characteristics
>>and status of both printers and jobs queued for the printer."
>>>>In section 2.1.4, Submitting a print job, change the 4th sentence
>>to read "Printing by reference is defined as submitting a job
>>and providing a reference to an existing document."
>>>>In section 2.1.5, Viewing the status of a submitted print job, change
>>the first sentence to read "After a job has been submitted to a
>>printer, the end -user needs a way to view the status of that job
>>(i.e. job waiting, job printing, job done)."
>>>>>