Peter - thanks for the input.
A revision to show that registration takes place with the Cloud Print
Provider (creating a Cloud Print Service) seems to be appropriate. This
appears to match with existing implementations where a print device can be
configured as an output destination for a cloud provider. Having the
registration done from the Cloud Print Manager would work for individual
print devices with embedded Cloud Print Managers (from a front panel or
remote interface), and a Cloud Print Manager for multiple devices hosted on
a workstation/server. It seems there would also be a way for an enterprise
to register multiple devices at the same time.
In the discussions at the F2F, there was only one Cloud Print Service
created to each instance of the Cloud Print Managers, but there could be
multiple registrations initiated by a Cloud Print Manager that reflect
different capabilities and/or devices (color, monochrome, duplex, special
paper). This sounds confusing - maybe a Cloud Print Manager Service or
other term for the portion of the Cloud Print Manager that talks to the
Cloud Print Service?
Larry
From: Zehler, Peter [mailto:Peter.Zehler at xerox.com]
Sent: Monday, May 14, 2012 5:20 AM
To: larryupthegrove; cloud at pwg.org
Subject: RE: [Cloud] Cloud white board diagram from meeting - converted
tovisio/pdf
All,
The main problem I have with the diagram is that it shows a Cloud Print
Manager registering with the Cloud Print Service instead of the Cloud Print
Provider. In my (protocol centric) view a upon the receipt of a
registration request from a Cloud Print Service, or its agent, the Cloud
Print Provider instantiates a cloud environment specific implementation of a
Cloud Print Service. The requirements for that implementation are that it
implements the PWG Print Service interface, exposes the appropriate objects
and attributes, and externally conforms to the state models codified in the
PWG model. At a later time the Cloud Print Manager will bind to the Cloud
Print Service to provide updated status and capability information and to
process Print Jobs destined for the physical printer(s) associated with the
Cloud Print Manager.
I expect the normal cardinality would be one physical device per Cloud Print
Manager and One Cloud Print Manager per Cloud Print Service. The PWG model
accommodates both Fan-Out and Fan-In of Printers. This allows a Cloud Print
Manager to "front end" a number of physical printers. Those printers can be
collocated (i.e., printer farm) or distributed (e.g., FedEx printer in
Google Cloud Print). Alternatively a single physical device could be
associated with a Cloud Print Manager that registers multiple Cloud Print
Services. The purpose of such a configuration could be to present different
capabilities and/or different defaults for each of the Cloud Print Services.
The [Print] Client is shown sending an Association request to the Cloud
Print Provider. Once the association is established and based on the
policies in place for the associated user, a set of Cloud Print Services
will be visible to the [Print] Client. The [Print] Client can then interact
(e.g., query status, query capabilities, submit print jobs) with the Cloud
Print Service.
Pete
Peter Zehler
Xerox Research Center Webster
Email: Peter.Zehler at Xerox.com
Voice: (585) 265-8755
FAX: (585) 265-7441
US Mail: Peter Zehler
Xerox Corp.
800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701
From: cloud-bounces at pwg.org [mailto:cloud-bounces at pwg.org] On Behalf Of
larryupthegrove
Sent: Friday, May 11, 2012 7:05 PM
To: cloud at pwg.org
Subject: [Cloud] Cloud white board diagram from meeting - converted
tovisio/pdf
ftp://ftp.pwg.org/pub/pwg/cloud/white/Cloud model representation.vsd
ftp://ftp.pwg.org/pub/pwg/cloud/white/Cloud model representation.pdf
Please review and I'll update drawing before inserting into the cloudmodel
draft.
Larry
--
This message has been scanned for viruses and
dangerous content by <http://www.mailscanner.info/> MailScanner, and is
believed to be clean.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/cloud/attachments/20120514/6778d224/attachment-0002.html>