RE: IPP> ipp: / http: in the UI
"Bennett, Joel H" <Joel.Bennett@usa.xerox.com> Wed, 15 July 1998 20:07 UTC
Delivery-Date: Wed, 15 Jul 1998 16:07:46 -0400
Return-Path: ipp-owner@pwg.org
Received: from cnri.reston.va.us (ns [132.151.1.1])
by ietf.org (8.8.5/8.8.7a) with ESMTP id QAA24259
for <ietf-archive@ietf.org>; Wed, 15 Jul 1998 16:07:45 -0400 (EDT)
Received: from lists.underscore.com (uscore-1.mv.com [199.125.85.30])
by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id QAA17080
for <ietf-archive@cnri.reston.va.us>; Wed, 15 Jul 1998 16:07:42 -0400 (EDT)
Received: from localhost (daemon@localhost) by lists.underscore.com
(8.7.5/8.7.3) with SMTP id QAA02170 for <ietf-archive@cnri.reston.va.us>;
Wed, 15 Jul 1998 16:07:43 -0400 (EDT)
Received: by pwg.org (bulk_mailer v1.5); Wed, 15 Jul 1998 16:03:31 -0400
Received: (from daemon@localhost) by lists.underscore.com (8.7.5/8.7.3) id
PAA01608 for ipp-outgoing; Wed, 15 Jul 1998 15:52:22 -0400 (EDT)
Content-return: allowed
Date: Wed, 15 Jul 1998 11:34:32 PDT
From: "Bennett, Joel H" <Joel.Bennett@usa.xerox.com>
Subject: RE: IPP> ipp: / http: in the UI
To: "'Paul Moore'" <paulmo@microsoft.com>, "'Jay Martin'" <jkm@underscore.com>
Cc: "'ipp@pwg.org'" <ipp@pwg.org>
Message-id: <C565EF2D2B51D111B0BD00805F0D7A72727DC1@USA0111MS1>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.0.1460.8)
Content-type: text/plain; charset="iso-8859-1"
Sender: owner-ipp@pwg.org
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA24259
I'm just beginning to get a handle on this, but do most of you envision this "ipp://printer" or "http://printer:633" or "printo:printer" being handled by the users web client (ie netscape)? I had assumed that most companies would want to develope their own clients, and that in the future users would be able to choose any company's client they preffered, or even a free/share-ware solution. IF you ARE talking about the necesity of developing specialized internet print clients (as opposed to a java client that loads from a web page or some-such), then it seems to me that you would want to settle on a scheme such as "printto:" or "printer:" which would in fact call up a seperate client. How are most of you planning on this being implemented? (do you really want to trust your printer's interface to the MS/Netscape war?) Original Message: _____ From: Paul Moore [mailto:paulmo@microsoft.com] You misunderstand my suggestion. I mean that printto: is like mailto: - it loads a client and passes in the destination address. It has nothing to do with the protocol that gets used to send the print. As always, in HIS hands, Joel H. Bennett <mailto:Joel.Bennett@usa.xerox.com> <http://jbennett.home.ml.org/> _____ QOTD: Dictatorship (n): a form of government under which everything which is not prohibited is compulsory. _____
- IPP> ipp: / http: in the UI Paul Moore
- Re: IPP> ipp: / http: in the UI Jay Martin
- RE: IPP> ipp: / http: in the UI Paul Moore
- RE: IPP> ipp: / http: in the UI Bennett, Joel H
- RE: IPP> ipp: / http: in the UI Harry Lewis