MySQL Forums
Forum List  »  MySQL Network and You

Re: Licensing question
Posted by: Arjen Lentz
Date: April 03, 2005 07:08PM

KimSeong Loh wrote:
> The article listed some possibilities for Developers.
>
> Case 4: Does "link with the MySQL server" means using MySQL server in embedded mode only or
> does it include using the client libraries to connect to a MySQL database server through TCP/IP or
> other protocol?
> For example: a java application using Connector/J or an application using ODBC.

It is about linking with MySQL code.
It definitely applies to libmysqld (the embedded server), as the server is GPL.
It also applies to the libmysqlclient (the client library), in case the application is not open source; the client lib is GPL, but has the licensing exception to allow other open source licensed apps to link with it too.


> Case 5: Certifying the application for use with MySQL Network.
> Does it mean distributing a certified application (non-GPL) do not need a commercial license to use
> the MySQL client library or drivers such as Connector/J or MyODBC?

Certified apps have nothing to do with commercial licenses as such.
It is about certifying that the app works with the certified server. This allows the app vendor to specify a known suitable environment for the application, and provide support based on that.

> Is it compulsory for the customer who buy the application to subscribe to MySQL Network or is it
> optional?

It is their choice, but the app vendor may even decide to only support the app if a certified server is used. This makes sense as it can be difficult (if not impossible) to provide support for an environment you don't know. If for example the user decides to compile their own server, there's no telling what can go wrong.


> What about cases where the developers create custom applications (non open source) for each
> customers?
> In the case of distributing a php application (non open source) which connects to a MySQL database
> through php mysql api, does this falls under case 3, case 4 or case 5? Definitely not case 1 and 2.

Again, it primarily comes down to what requirements an application builder has.
It makes sense to be a MySQL partner for MySQL Network, so you have those resources available, the exposure on the MySQL web site, and providing the known tested environment to users.

We could debate the (sometimes murky) legal bottom line, but that's not it's really about.
MySQL Network for end users, and network/oem partnerships for developers, offers an environment that provides real value for all those involved. It's also very affordable.
Inside any of these offers, licensing effectively becomes a non-issue. So why waste time on it?

Regards, Arjen.
--
Arjen Lentz, Exec.Director @ Open Query (http://openquery.com)
Remote expertise & maintenance for MySQL/MariaDB server environments.

Follow us at http://openquery.com/blog/ & http://twitter.com/openquery



Edited 1 time(s). Last edit at 04/03/2005 07:09PM by Arjen Lentz.

Options: ReplyQuote


Subject
Written By
Posted
April 02, 2005 07:46AM
Re: Licensing question
April 03, 2005 07:08PM
April 14, 2005 12:01PM
April 14, 2005 07:52PM
May 01, 2005 07:00PM
March 01, 2006 04:28PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.