From: Michael Sweet <mike@easysw.com>
To: "McDonald, Ira" <imcdonald@sharplabs.com>
Cc: "'Hastings, Tom N'" <hastings@cp10.es.xerox.com>,
printing-architecture@freestandards.org,
"'ipp@pwg.org'" <ipp@pwg.org>
Subject: [Printing-architecture] Re: IPP> FW: Summary of PWG Document Object issues
Date: Fri, 25 Apr 2003 15:17:20 -0400 [thread overview]
Message-ID: <3EA989C0.4000400@easysw.com> (raw)
In-Reply-To: <116DB56CD7DED511BC7800508B2CA53735CF9E@mailsrvnt02.enet.sharplabs.com>
McDonald, Ira wrote:
> Hi Tom,
>
> I disagree entirely with your reasoning below.
>
> The main purpose of PSI is print-by-reference. If Send-URI
> remains OPTIONAL (and therefore rarely implemented and not
> interoperable) in IPP, then gateways based on FSG PAPI/1.0
> interfaces between PSI and IPP transports will fail (unless
> the gateway fetches the referenced document, which introduces
> a different set of security issues).
>
> This isn't a percentage kind of thing. The most important
> operation in PSI is AddDocumentByReference. All of the mobile
> scenarios depend on it. Mobile devices _cannot_ fetch local
> copies of large documents, in order to use AddDocumentByValue.
Well, if mobile devices cannot fetch large documents (to display
them), then printing them is a bit useless, right? Better to just
provide web-enabled applications for wireless devices to access
when they need to handle large documents.
The only operational scenario that I see where this would make *any*
sense is when viewing a large PDF file that has been linearized
("optimized") for the web, and even then you cannot have a proxy
between the client and server or none of the byte serving (which
allows a light-weight client to view the PDF file in pieces) will
work anyways.
I have yet to be convinced that print-by-reference is anything other
than a "gee wiz" feature.
--
______________________________________________________________________
Michael Sweet, Easy Software Products mike at easysw dot com
Printing Software for UNIX http://www.easysw.com
next prev parent reply other threads:[~2003-04-25 19:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-25 18:38 [Printing-architecture] RE: IPP> FW: Summary of PWG Document Object issues McDonald, Ira
2003-04-25 19:17 ` Michael Sweet [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-25 0:19 Hastings, Tom N
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EA989C0.4000400@easysw.com \
--to=mike@easysw.com \
--cc=hastings@cp10.es.xerox.com \
--cc=imcdonald@sharplabs.com \
--cc=ipp@pwg.org \
--cc=printing-architecture@freestandards.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.