Dear developers,
we published an open source live compositing software some months ago. It has a COM interface, and now we want to add a TCP/IP interface. Literally, the COM interface is not fast enough at the moment, but that's a different problem.
The current COM interface including events is described here: [login to view URL]
The interface needs to be bidirectional. Example: The client sends a "PLAY" signal and a video starts playing at the server. When the video is at the end, an event must be fired back to the client software.
The new interface must implement all methods and events from the existing COM interface. It is important that the interface does not have any impact to the performance of the software (new threads?), because the software is a real time video compositing software.
The entire source code is public; you can find it at [login to view URL] .
You are required to
- write the new interface code
- commit the changes via GIT
- write an example client software (C# or VB.NET) which allows to test the new interface easily (all functions) manually, including automatic demo of all possibilities
- update the official wiki with information about the new interface, including code samples
We are happy about your proposals regarding ...
- Protocol, port, ...
- threading, performance
- further ideas