While studying the architecture of the configuration files, you may think of various ways to implement the concept into an installation process.
Some possible scenarios:
1. CD installation, device configuration instance on CD
1.1. the traditional way
all files are on the CD. the references to instance names are pure file names, no path included.
1.2. web site reference
all files are on the CD, but only get used as a fallback. the references to instance names are URLs. depending on the installer the URLs are used automatically or as default (install from CD as second choice).
keep in mind that the option configuration references can point to completely different web sites from third-party developers.
2. network installation
not too much different from the two CD methods.
3. Device installation, device configuration instance in device
it is not necessary to store more than this single instance in the device.
all other files could be pulled from web sites or as a fallback from CD.
this allows for a driver independent installer. imagine the operating system has a generic UPDF driver installed already (and if not, it knows where to find at least one), it could pull the single device configuration file from the device and would find all other information in there.
I see various combinations of the different methods.
keep in mind that any option configuration stays separate, even after installation, and can therefore be disconnected or updated at any time without hurting the installation of the base unit and any other optional unit.
These scenarios are not described in the specification document.
just some personal ideas.
69 Prescott Drive
This archive was generated by hypermail 2b29 : Wed Mar 03 2004 - 11:56:39 EST