Looking for architectures that avoid GPL contamination
-
I am looking for ideas for avoiding contamination of proprietary code by a GPL application. I need to be able to use the GPL application without opening up my code to GPL. I would like to get feedback from folks who may have encounter this issue and considered using some RPC mechanism to establish client/server type architecture potentially using shared memory for data passing. This is for a multimedia type application. Thanks. Fred
-
I am looking for ideas for avoiding contamination of proprietary code by a GPL application. I need to be able to use the GPL application without opening up my code to GPL. I would like to get feedback from folks who may have encounter this issue and considered using some RPC mechanism to establish client/server type architecture potentially using shared memory for data passing. This is for a multimedia type application. Thanks. Fred
If I understand GPL correctly, you are toast either way. If you derive, use, intaract with a GPL product you have to go GPL. The only way I know of to bypass it is to ask the developers if you may buy the right to use it w/o GPL.
Blog: http://www.rogeralsing.com Projects: http://www.puzzleframework.com
-
I am looking for ideas for avoiding contamination of proprietary code by a GPL application. I need to be able to use the GPL application without opening up my code to GPL. I would like to get feedback from folks who may have encounter this issue and considered using some RPC mechanism to establish client/server type architecture potentially using shared memory for data passing. This is for a multimedia type application. Thanks. Fred
Simple answer - find an alternative component that doesn't use GPL. Maybe find one that uses LGPL or is closed source. You can't arbitrarily decide to ignore the GPL license - the author's have decided to license the component that way, and if you use it you agree to abide by the decision.
Deja View - the feeling that you've seen this post before.
-
I am looking for ideas for avoiding contamination of proprietary code by a GPL application. I need to be able to use the GPL application without opening up my code to GPL. I would like to get feedback from folks who may have encounter this issue and considered using some RPC mechanism to establish client/server type architecture potentially using shared memory for data passing. This is for a multimedia type application. Thanks. Fred
Fred Garvin wrote:
avoiding contamination of proprietary code by a GPL application
This sounds like a twist in reality, are you an IT manager? ;) Anyway, here are some possibilities. First, there speaks nothing against using GPL-ed applications, e.g. using the Apache web server does not require your web applications or content to fall under the same license. Secondly, consider contacting the author (copyright holder) and ask if you may purchase the product under an alternative license, e.g. some software is dual-licensed to fit proprietary needs. Finally, consider going open source yourself and possibly benefit from community/developer feedback. Hope it helps. /M
My Webchat :java:
-
Fred Garvin wrote:
avoiding contamination of proprietary code by a GPL application
This sounds like a twist in reality, are you an IT manager? ;) Anyway, here are some possibilities. First, there speaks nothing against using GPL-ed applications, e.g. using the Apache web server does not require your web applications or content to fall under the same license. Secondly, consider contacting the author (copyright holder) and ask if you may purchase the product under an alternative license, e.g. some software is dual-licensed to fit proprietary needs. Finally, consider going open source yourself and possibly benefit from community/developer feedback. Hope it helps. /M
My Webchat :java:
That is in part because the Apache web server is licensed under the Apache license - which is not very much like the GPL at all...
Mark Churchill Director Dunn & Churchill Free Download:
Diamond Binding: The simple, powerful, reliable, and effective data layer toolkit for Visual Studio.