I'm writing a program for automation under a license that is incompatible with GPLv2 (it's dual-licensed: GPLv3/Proprietary). Let's call it my automation program.
And there is third party GPLv2 program that supports plugins.
I want to write and distribute a remote control plugin under GPLv2 license for GPLv2 program that adds ability to this program to be controlled via websocket protocol. It links as "*.dll" file with it. As I understand I'm allowed to do it.
But am I allowed then to make my automation program to control this GPLv2 program via websocket protocol (thanks to the plugin)?
- Both programs run separately and can do their jobs not relying on each other. For example, my automation program does many other things, but communicating with GPLv2 program gives it additional feature.
- My automation program will be able to communicate with few other programs with functionality similar to GPLv2 program.
- The plugin to the GPLv2 program will allow it to be remotely controlled with any other program using my API, not only with My automation program. And it will be useful for the user.
- My automation program will most likely communicate with GPLv2 program not over the network, but on the same machine.