Hi David, > This requirement isn't worded correctly, I can see how this would > imply this service would do the logging. I will work on this. >> 5. Driver Verification Service, page 20: >> 5.2 Requirements, item 5: Isn't querying repositories for the latest >> versions of the driver a duplication of what the ITU Service does? >> >> > That's an interesting question. So far we don't have the ITU doing > the querying for the latest drivers, it simply takes the data from the > driver verification and downloads the drivers as requested. So, in > essence the ITU is simply a download and update miniroot mechanism. > Along with a few other details that I am hand waving on right now. Our > current ITU simply takes input from the user about where the driver is > they want to update the install environment with. > > As I think about this it seems to me that driver verification is the > correct place for this querying, and locating of the missing drivers. > It is the service that is checking which devices are on the system, > and has to know if it can even get drivers for these devices. So, it > has as list of repositories it can look through to determine what > drivers might be available for download. I actually looked at our diagrams regarding this sequence(2.1.2) and realize that we show the ITU locating missing drivers. I think this could be where part of your question comes from. We are inconsistent ourselves in this document. So... let me look at this some more and revise this. I still think the driver verification has to try to locate the appropriate drivers so that the ITU service knows what to download. But, this needs more thought and more understanding on my part about what the ITU service will and can do.
thanks, sarah
