ECJ-INTEREST-L Archives

December 2009

ECJ-INTEREST-L@LISTSERV.GMU.EDU

Options: Use Monospaced Font
Show HTML Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
ECJ Evolutionary Computation Toolkit <[log in to unmask]>
Date:
Fri, 18 Dec 2009 21:57:11 +0100
MIME-version:
1.0 (Apple Message framework v936)
Reply-To:
ECJ Evolutionary Computation Toolkit <[log in to unmask]>
Content-type:
text/plain; charset=US-ASCII; format=flowed; delsp=yes
Subject:
From:
Sean Luke <[log in to unmask]>
In-Reply-To:
Content-transfer-encoding:
7bit
Comments:
To: ECJ Evolutionary Computation Toolkit <[log in to unmask]>
Parts/Attachments:
text/plain (20 lines)
The Affero GPL is baffling, and iText's use of it is even more so.   
There is surprisingly little data about this license and its effects,  
and it doesn't give me a warm and fuzzy feeling.

Affero is meant to prevent people from using GPL code on their servers  
which provide network services of some sort (like SOAP or ASP or  
whatnot) for other systems.  Such servers must provide the source to  
their code via HTTP I think. But it's written so broadly that it's  
hard to tell whether this applies in other situations.  For example,  
if you offer a MASON applet over the web, and even offer the code on  
your web page, are you still required to have a facility on your  
applet to serve its own source code to people who want it?  This would  
depend on whether or not the original iText  source offered such a  
facility.  But you're required to find that out, which so far as I can  
tell means scouring their source.

Why in the world iText is using this is beyond me.

Sean

ATOM RSS1 RSS2