home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!not-for-mail
- From: duke@osf.org
- Newsgroups: comp.std.unix
- Subject: There is a printing API in 1003.7.1 (Was Re: IMPORTANT: POSIX threatens our use of l)
- Date: 22 Jan 1993 10:58:04 -0800
- Organization: Kithrup Enterprises, Ltd.
- Lines: 27
- Sender: sef@ftp.UU.NET
- Approved: sef@ftp.uucp (Moderator, Sean Eric Fagan)
- Message-ID: <1jpg3sINN3l8@ftp.UU.NET>
- Reply-To: duke@osf.org
- NNTP-Posting-Host: ftp.uu.net
- X-Submissions: std-unix@uunet.uu.net
-
- Submitted-by: duke@osf.org
-
- geoff@tyger.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top) writes:
- >Actually, the biggest pain in the ass is not the printing commands, or
- >even the administration model. It's the absence of a standard printing
- >API. ....
- >It's been a while since I looked at the palladium doc (I've just
- >pulled DEC-palladium-overview.ps over from gatekeeper.dec.com - it's in
- >/.3/net/info/ietf/print-wg - and I'll read it over), but I don't recall
- >there being any kind of API which would be suitable for cross-platform
- >uses.
-
- Palladium defines two APIs you could use to write print clients. One
- is real high level--each command has a function version. The other
- is much lower level. It lets you build up print requests and submit
- them to a spooler. Chapter 4 of the POSIX draft is this second api.
-
- >Maybe we should just define a printing API. Nail down a really
- >straightforward interface (just half a dozen calls or so),
-
- The Palladium one is more complicated than that, since there's so
- much more stuff to do in Palladium than in, for example, lpr/lpd.
-
- Bob Robillard, Technical Editor 1003.7.1, duke@osf.org
-
-
- Volume-Number: Volume 30, Number 36
-