Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


To master this today several solutions, communication protocols and framework are created. Some of them are proprietary and close sourced, some of them are open source and used also in non IVI environments. To handle this challenge also in the future a standardization and robust implementation of sharing technologies is required and categorization of a existing technologies is a an good step forward into this direction.

Sometimes it might be difficult to assign a concrete sharing technology to a single category, because of some implementation details it might fit to several categories at the same time but this is not a concern of this white paper. In first place categories should provide an abstraction of a complex technologies to be able to design the system without a detailed understanding of concrete implementation.

Following five categories are suggested:


They are described and compared to each others in the following captures. [TODO] Sentence about the fact that  categories are not a strict separation between the technologies, some of them are sitting in between, they should provide an abstraction to a complex implementations to be able to design the system without a detailed understanding of concrete technology and corresponding implementation.

API Remoting

API Remoting involves taking an existing graphics API and making it accessible through a network protocol, thus enabling one system to effectively call the graphics/drawing API of another system. In some cases an existing programming API such as that of a local graphics library (e.g. OpenGL), is simply extended to provide network-capability turning it into an RPC (Remote Procedure Call) interface. In other cases, new custom programming interfaces might be created that are specially tailored for distributed graphics.