On Thu, Nov 18, 2004 at 10:12:29PM -0500, Krzysztof Kamieniecki wrote:
blocks. This server program transmits an MPEG2 transport stream through a
TCP/IP socket and accepts commands through another TCP/IP socket. Then you
write a proprietary client program that connects to this ATSC receiver
server through the TCP/IP ports. The ATSC receiver would definitely have to
licensed under GPL. What about the client program? Would this depend on
what type of API the ATSC server has?
The GPL only cares about "derivative works" in the copyright sense.
If your client application cannot be considered a derivative work of
the original GPLed application, then the GPL does not apply to it.
The goal of the GPL is not to "infect" other applications. The goal is
to protect copyrighted works licensed under the GPL. If your activities
don't infringe on the rights of the copyright holders whose work is
licensed under the GPL, then there's no issue.
So basically, if your application communicates with a GPLed application
merely through an API or network interface, and doesn't need to use GPLed
code to do that, then you're in the clear and can do whatever you want
with your application.
If this weren't so, then web browsers would be GPL-infringing the moment
they requested a web page from a GPL-licensed web server.
Regards,
David