Virtual Devices: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[de:Was_sind_virtuelle_Ger%C3%A4te%3F]] | |||
An application profile defines virtual devices. Their advantage is the fact, that several virtual devices can be merged to a single physical device. So it can be chosen, which of the defined functionalities shall be located in which physical device. As every device which could be connected to the system is already defined in an application profile, the communication between the devices can be pre-defined. This is required for a plug-and-play system. | An application profile defines virtual devices. Their advantage is the fact, that several virtual devices can be merged to a single physical device. So it can be chosen, which of the defined functionalities shall be located in which physical device. As every device which could be connected to the system is already defined in an application profile, the communication between the devices can be pre-defined. This is required for a plug-and-play system. | ||
There is no master/slave-communication, because every virtual device can communicate with every other one. The communciation is described in the so called pre-defined connection set. | |||
Latest revision as of 18:23, 10 January 2007
An application profile defines virtual devices. Their advantage is the fact, that several virtual devices can be merged to a single physical device. So it can be chosen, which of the defined functionalities shall be located in which physical device. As every device which could be connected to the system is already defined in an application profile, the communication between the devices can be pre-defined. This is required for a plug-and-play system.
There is no master/slave-communication, because every virtual device can communicate with every other one. The communciation is described in the so called pre-defined connection set.