Michael,
Thanks for comments. Arrows fixed, I'll remove the first four operations
and add the
starting state in the descriptive paragraph. Also the change you suggested
will become:
The Printer is already registered in the Cloud and the Client is associated
with the Cloud Print Service.
All,
Since the Cloud Print Manager initiates the communication with the Cloud
Print Service, should there be a sequence drawing for initial
communications? I could see this also as part of the Imaging model, where
the configurations and capabilities for the other services are sent to the
appropriate cloud service.
Larry
From: Michael Sweet [mailto:msweet at apple.com]
Sent: Thursday, December 06, 2012 2:33 PM
To: larryupthegrove
Cc: cloud at pwg.org
Subject: Re: [Cloud] Updating cloud printing sequence diagrams to an
improved format
Larry,
On 2012-12-06, at 5:12 PM, larryupthegrove <larryupthegrove at comcast.net>
wrote:
<ftp://ftp.pwg.org/pub/pwg/cloud/white/Cloud Print Sequence drawing
revision 12_6.vsd> ftp://ftp.pwg.org/pub/pwg/cloud/white/Cloud Print
Sequence drawing revision 12_6.vsd
<ftp://ftp.pwg.org/pub/pwg/cloud/white/Cloud Print Sequence drawing
revision 12_6.pdf> ftp://ftp.pwg.org/pub/pwg/cloud/white/Cloud Print
Sequence drawing revision 12_6.pdf
I redid the initial sequence drawing to incorporate the suggestions and
discussions from the 12/5 face to face meeting.
I would appreciate feedback or suggestions before I update all the other
sequence drawings.
I like the new format, although I would stick with the same arrow head style
for all of the lines representing requests.
As for the specific content, you probably don't want to show the initial
four Update operations on the Cloud Print Manager side. If you *do* show it,
the timeline should be broken up and the UpdatePrintJobState and
UpdatePrintDocumentState operations removed since, on startup, the Cloud
Print Manager will just send UpdatePrintServiceState and
UpdateFetchablePrintJobs to reset things to a known state.
UpdatePrintJobState and UpdatePrintDocumentState would only be called for
jobs that were being processed during a prior run.
I am also going to add a descriptive paragraph for each sequence drawing.
For the revised drawing:
This sequence drawing represents the operations for a print submittal which
contains a single document.
No errors occur in the document or in the print processing.
The Printer is already registered in the Cloud and the User is associated
with the Cloud Print Service.
I think you mean "The Client is associated" since you don't show the User in
the diagram, right?
Thanks for any suggestions!
Larry
--
This message has been scanned for viruses and
dangerous content by <http://www.mailscanner.info/> MailScanner, and is
believed to be clean. _______________________________________________
cloud mailing list
<mailto:cloud at pwg.org> cloud at pwg.org
<https://www.pwg.org/mailman/listinfo/cloud>
https://www.pwg.org/mailman/listinfo/cloud
________________________________________________________________________
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/20121206/10f6bb07/attachment-0002.html>