Why is the DCM stored in a BAV device, instead of simply indicating a URL where it can be downloaded from?
While downloading the DCM from a URL does have some benefits (such as eliminating the need for a DCM to be embedded in a device and having the ability to download the latest DCM), there are some drawbacks to having the DCM only available from a URL: • Each time the device is connected, its DCM would have to be downloaded from the URL and installed. This takes time due to the (usually slow) Internet connections, forcing the user to wait for the download. • To run the downloaded DCM, an FAV device containing Java Virtual Machine is usually required, forcing the end-user to purchase a relatively costly FAV device. • If the URL cannot be accessed for some reason (network connection problems, etc.) then the device’s DCM cannot be downloaded and thus it cannot be controlled.
Related Questions
- If there are multiple FAV devices, is it possible that the DCM of a BAV device could be loaded by more than one FAV device, creating a conflict?
- Why is the DCM stored in a BAV device, instead of simply indicating a URL where it can be downloaded from?
- Where is the CriticalBlue microcode stored and how is it downloaded onto the coprocessor?
