Subject: Re: Ximian's proprietary connector for open source Evolution
From: burton@openprivacy.org (Kevin A. Burton)
Date: 05 Dec 2001 17:34:24 -0800

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ben Laurie <ben@algroup.co.uk> writes:

> "William C. Cheng" wrote:
> > 
> > Greetings,
> > 
> > Any one knows how Ximian is getting away (or not) with mixing proprietary
> > "connector" software with an open source base?  Is it the good-o dynamic
> > linking does not violate GPL type of argument?

I think the broader question is.  Is RPC a linkage?  I think it might be.
Usually a linkage is explicit.

#include <string.h>

or

import java.lang.String;

SOAP/xmlrpc, etc I think is an include.  You need to specify service name,
connection URL, methods, params, etc.

The only problem is that if you are connecting to a standardized interface, you
might be in violation of that interface's implementation.

IE if you call a helloWorld() method from a MS client to a GPL server, chances
are that the MS client is not GPL compatible :)

What is needed in this situation I think is the MODULE_LICENSE macro AKA the
newest Linux kernel.

Some new linux system calls can require that they are ONLY executed from GPL
only code.  If you attempt to call a GPL_ONLY system call from a non GPL
MODULE_LICENSE you will now get linkage.

I think that this could be held up in court as an explicit licensing agreement.
AKA EULA....

Kevin

- -- 
Kevin A. Burton ( burton@apache.org, burton@openprivacy.org, burtonator@acm.org )
             Location - San Francisco, CA, Cell - 415.595.9965
        Jabber - burtonator@jabber.org,  Web - http://relativity.yi.org/

$live{free} || die "";
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Get my public key at: http://relativity.yi.org/pgpkey.txt

iD8DBQE8Dsr/AwM6xb2dfE0RAhKLAKCArRUaZq2ynInJAv/0ARe2ntI1dQCfcHWg
iO9lGnW1FZVCDnJx9dkGSrI=
=6UVd
-----END PGP SIGNATURE-----