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.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!
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean. _______________________________________________
> cloud mailing list
>cloud at pwg.org>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...