From: Norm Jacobs <Norm.Jacobs@Sun.COM>
To: printing-discuss@freestandards.org,
printing-architecture@freestandards.org
Subject: [Printing-architecture] FSG Printing Diagram - 10,000,000ft view
Date: Thu, 12 Sep 2002 14:41:05 -0500 [thread overview]
Message-ID: <3D80EDD1.4CB90168@Sun.COM> (raw)
[-- Attachment #1: Type: text/plain, Size: 849 bytes --]
I ran this by Pete and he suggested that I send it out.
-Norm
The drawing I attached is in line with the level that I was
hoping we would start with. I may have oversimplified some of
of it and maybe we need more detail than I have provided. It's
missing things, but it highlights the interfaces we are working.
Application
This could be CLI/GUI applications run by users that
interact with the print service. It may also include
server side protocol implementations/gateways (e.g.. rfc-1179,
IPP, SMB, ...)
JTAPI
Job ticket generation (possibly processing)
PAPI
Job/Printer/Spooler Interface for Applications. The
implementation(s) of this API incorporate Print Service
specific information (protocol, spooler, etc.)
CAPAPI
Capabilities
Print Service
...
[-- Attachment #2: FSG-10000000ft.jpg --]
[-- Type: image/jpeg, Size: 49183 bytes --]
reply other threads:[~2002-09-12 19:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3D80EDD1.4CB90168@Sun.COM \
--to=norm.jacobs@sun.com \
--cc=printing-architecture@freestandards.org \
--cc=printing-discuss@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.