3 ms·
Its a little different than the GPL. If you modify some GPL server code, and open that server up to "public" connections, you don't have to contribute back your
by psadauskas 16y ago
Its a little different than the GPL. If you modify some GPL server code, and open that server up to "public" connections, you don't have to contribute back your changes, as long as you don't distribute the server itself.
With the AGPL, however, you do. Some people, though, interpret that to also mean that any of your code that connects to an AGPL server must also be open-sourced; eg, you web app, if it connects to mongodb, you must provide the source. As far as I know, there's been no legal opinion if thats the case, and the mongodb devs have stated thats not how they read it, and thats not what they intend.
- ianb 16y agoI don't think anyone could argue that if you had an AGPL HTTP server that the AGPL would be applicable to browsers that connected to the server. So if the Mongo protocol is presented as an open protocol it seems unambiguous. Though if someone created an "open" protocol to someone else's AGPL code with the clear intention of bypassing the AGPL... it might get weird and awkward.
- psadauskas 16y agoRight, but I don't think anyone is arguing that. Its when you modify the AGPL server code, and open that up, you have to release your modification. So in you AGPL HTTP server example, the clients never are required to be open, but any changes you make to the server must have the source available.