VideoOverIP supports two modes of operation which determine how it captures video information from the source:
1. Mirror Driver Mode
Using this methodology, VideoOverIP relies on a mirror driver that is included with the host installer. The mirror driver is used to intercept rendering calls and capture screen changes via an event-based model. These changes are then processed by the VideoOverIP change detection, optimization, and compression pipelines before being sent to the receiver or client. This technique aims to be more efficient by reducing the CPU usage on the host or sender side.
2. GDI Mode
Using this methodology, VideoOverIP uses Graphics Device Interface (GDI) methods to capture the frame buffer and does not rely on an event-based approach to be notified of on-screen changes. This technique has the advantage of capturing the final, processed image from the frame buffer which allows the protocol to support Windows Aero or other sophisticated display technologies which require a host-side GPU. The downside with this approach is the increase in host-side CPU utilization due to the extra polling employed for source-side video capture.
VideoOverIP does not require a connection broker to operate, but it is fully supported by VDIworks' VDP connection broker2 and virtual desktop management software.
VideoOverIP provides the following major features:3
"VDIworks releases new VDI remote desktop connection protocol". Brianmadden.com. Retrieved 2009-06-18. http://www.brianmadden.com/blogs/gabeknuth/archive/2009/06/18/vdiworks-releases-new-VDI-remote-desktop-connection-protocol-yawn-or-yay.aspx ↩
"VideoOVerIP Product Page". VDIworks.com. Retrieved 2009-04-30. http://www.vdiworks.com/?q=videooverip ↩
"VideoOverIP Data Sheet" (PDF). VDIworks.com. Retrieved 2009-06-18. http://www.vdiworks.com/datasheets/VideoOverIPDatasheet.pdf ↩