system automation for multiplatforms

---

Does the node-locking mechanism follow generally-accepted computer science principles, and not do such tricks as bypassing the operating system, with all its unforeseeable consequences (such as

breaking just because the user installed a boot manager, or upgraded their operating system)?
* Can you secure licenses on virtualized systems (e.g. VMWare), where the hardware parameters can legitimately change for a licensed user? How about supporting users who run Windows on a Mac?
* If you want, can the node-locking mechanism provide resiliency against small changes, so not inconveniencing users who make a minor system upgrade?
* Can you specify a set of locking parameters, with the license working if any one of them is matched? For example, perhaps your user wants to be able to run their license in one of any four

machines - can you accommodate this?
* If some users really prefer dongle-based licensing, can you lock to a dongle as well?
* If you sell a system with your own custom hardware in it, can you lock the license to, say, the serial number in your custom hardware?
* How do you deal with the inevitable 'My machine crashed - how do I restore my license?' user inquiry?
A short term victory that didn’t last very long…
So far so good, but here are some node-locking questions to ask:
In the realm of online videos, such as with Hulu, Youtube, Netflix and other video based services, there is more that goes on behind the scenes than most people think. There is more of a technical

side of the process that takes place that delivers video content from a server to the final output source, like your tv, mobile device, or computer screen. There is a process that goes on to make sure

that the video is displayed correctly, is at the right scale and resolution for the screen. There are ways to be able to get the same video to be displayed on multiple types of screens and formats. This

is called Multiplatform Video Processing.
system automation for multiplatforms

---