Bill,
On 2013-07-20, at 5:04 PM, William A Wagner <wamwagner at comcast.net> wrote:
> Hi Randy,
>> 1. Since it was decided that a Cloud Imaging Service could be associated with more than one device, we had to model a way to register a Device service with a pre-existing Cloud Service. There seemed no advantage in also modeling a mode where registering a device created the Cloud imaging service.
I don't think we decided that the Cloud Imaging Services were already created. But we *did* decide that they might already be created and reused, so rather than requiring a particular implementation with a new service for every device, we can simply have an operation that allows the Proxy to identify which services are available for the Proxy to use.
I think it is important to reflect this in the description of the Identify Services operation - a Cloud provider may do lazy creation (on first registration) of services in the device owner's account, or might just create services as part of the creation of the device owner's account. All of the details are out-of-scope, all we care is that the services exist (and are started) by the time the Cloud Imaging Control Service responds to the Identify Services request from the Proxy, right?
_________________________________________________________
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/20130722/506db03e/attachment-0002.html>