[Cloud] Feedback on proposed Cloud Print extensions

[Cloud] Feedback on proposed Cloud Print extensions

[Cloud] Feedback on proposed Cloud Print extensions

Michael Sweet msweet at apple.com
Mon Dec 3 16:02:09 UTC 2012


All,

I've posted this feedback in slide form at:

    ftp://ftp.pwg.org/pub/pwg/cloud/white/cloud-extension-comments-sweet-20121203.pdf

This feedback is based on my work on IPPSIX, the IPP binding spec for this stuff...

.....

GetAvailableJobs

- Don’t like being able to get jobs for multiple Printers

	- Doesn’t match existing SM or IPP Printer objects - the Client
	  is always talking to a single service endpoint/target, not
	  multiple services/targets

	- Existing model does not preclude having a Cloud Print Manager
	  that fronts multiple output devices

		- 1 Cloud Print Manager with multiple output devices
		  sharing the same Cloud Print Service, or

		- N Cloud Print Managers (implementation might merge
		  these) each using their own Cloud Print Service

- But why have GetAvailableJobs at all?
	- Existing GetJobs operation provides all the info needed
	- Notifications tell you which printer needs to be polled


FetchDocument

- Need basic transform functionality

	- Request that the document data be transformed to a
	  suitable format for printing, such as “I need PWG
	  Raster data in 8-bit grayscale at 300dpi”

	- This is used by Google Cloud Print and other
	  implementations

	- Also covers things such as copy generation, scaling,
	  number-up, etc.

- Cloud Print Service advertises capabilities
  (FetchDocumentElementsSupported,
   FetchDocumentPWGRasterDocumentTypesSupported,
   FetchDocumentPWGRasterDocumentResolutionsSupported)

- Cloud Print Manager includes DocumentTicket in FetchDocument
  request

	- Includes additional elements for output format
	  (DocumentFormat/Details, PWGRasterDocumentType,
	   PWGRasterDocumentResolution)

	- Cloud Print Service will need to fetch data from
	  Document URI

		- Do we define when that happens?
		- What about caching?


User Role “Printer”

- When characterizing access control policies, we often use
  “adminstrator”, “operator”, “user”, and “system” as user
  roles

- For Cloud Print we need a new role for the printer/ Cloud
  Print Manager

	- Printers can fetch documents, users probably can’t
	  (although there is a use case for users viewing
	   documents they have submitted...)

	- Most of the other Cloud Print operations are probably
	  printer-only

__________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


-- 
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/20121203/96d3b01f/attachment-0002.html>


More information about the cloud mailing list