You are developing a server side application in GPL. Now this application serves HTML and not an executable which is directly executed on your machine. That means that another guy could take the GPL code, adapt it and does not necessarily need to publish it. Ie. he can create the identical service using your software without violating the GPL. (Although THEN he cannot publish the software itself i.e. selling)
The GNU Affero General Public License is based on the GNU GPL, but has an additional term to allow users who interact with the licensed software over a network to receive the source for that program. We recommend that people consider using the GNU AGPL for any software which will commonly be run over a network.
发布评论
评论（2）
假设如下：
您正在使用 GPL 开发服务器端应用程序。现在，该应用程序提供 HTML，而不是直接在您的计算机上执行的可执行文件。这意味着另一个人可以获取 GPL 代码并对其进行改编，但不一定需要发布它。 IE。他可以使用您的软件创建相同的服务，而不会违反 GPL。 （尽管他不能发布软件本身，即销售）
AGPL< /a>.
GPL 中的这个漏洞通常被称为“应用程序服务提供商”漏洞。
搜索“Why AGPL”或“AGPL vs. GPL”，了解一些存在 GPL 问题的真实项目。
使用 AGPL 的公共 Web 应用程序在维基百科中列出。
Assume the following:
You are developing a server side application in GPL. Now this application serves HTML and not an executable which is directly executed on your machine. That means that another guy could take the GPL code, adapt it and does not necessarily need to publish it. Ie. he can create the identical service using your software without violating the GPL. (Although THEN he cannot publish the software itself i.e. selling)
Not so with the AGPL.
This hole in the GPL is often called "Application Service Provider" hole.
Search for "Why AGPL" or "AGPL vs. GPL" for some real projects who have problems with GPL.
Public web application that uses the AGPL are listed at wikipedia.
请参阅http://www.gnu.org/licenses/licenses.html#AGPL
See http://www.gnu.org/licenses/licenses.html#AGPL