Momentary Compliance
From GPLv3 Wiki
Revision as of 17:14, 3 March 2006 syeates (Talk | contribs) added test case ← Previous diff |
Revision as of 18:15, 3 March 2006 syeates (Talk | contribs) tweak Next diff → |
||
Line 1: | Line 1: | ||
- | Party A releases some software under the GPL3. Party B creates derivative software and releases it in binary form to Party C. Party C requests the source code from Party B. Party B puts the source up on a website but makes it accessible using time controls: for a single instant every 59 days the software is downloadable, otherwise . Even with a 60 day request flood of Party B's webservers, Party C may never get the software, but Party B can perpetually be within the 60 day grace period. | + | Party A releases some software under the GPL3. Party B creates derivative software and releases it in binary form to Party C. Party C requests the source code from Party B. Party B puts the source up on a website but makes it accessible using time controls: for a single instant every 59 days the software is downloadable, otherwise an appropiate HTTP error code is returned. Even with a 60 day request flood of Party B's webservers, Party C may never get the software, but Party B can perpetually be within the 60 day grace period. |
Back to [[Test Cases]] | Back to [[Test Cases]] |
Revision as of 18:15, 3 March 2006
Party A releases some software under the GPL3. Party B creates derivative software and releases it in binary form to Party C. Party C requests the source code from Party B. Party B puts the source up on a website but makes it accessible using time controls: for a single instant every 59 days the software is downloadable, otherwise an appropiate HTTP error code is returned. Even with a 60 day request flood of Party B's webservers, Party C may never get the software, but Party B can perpetually be within the 60 day grace period.
Back to Test Cases