[prev in list] [next in list] [prev in thread] [next in thread] 

List:       php-db
Subject:    Re: [PHP-DB] TUDBC a new unified database API for PHP (Phalanger, Quercus), Ruby (IronRuby, JRuby),
From:       "Post-No-Reply TUDBC" <post-no-reply () tudbc ! org>
Date:       2008-09-14 18:36:31
Message-ID: d036cbe50809141136r6c86bf6ex53c1b6ba07f44d13 () mail ! gmail ! com
[Download RAW message or body]

Thanks for your comment. I did some reading over the weekend.

There were so many types of licenses out there, and reading and
understanding all the details could be overwhelming. I read a bit
about GPL (GNU General Public License, read GPL wiki
http://en.wikipedia.org/wiki/GNU_General_Public_License for a start).
It is similar to what I have in several ways in my limited
understanding. For GPL, I was surprised to learn that you can modify,
but the modifications will belong to the public and not you. For dual
license similar to MySQL, I am still unclear how the public
contributed modifications can be kept out of the proprietary part,
because even two people write for the exact same purpose, the outcome
will be very similar, so how can you tell whether one actually copied
from another or not.

Until I have more time to sort things out, I don't know which license
suits TUDBC best.

At any rate, under my current license,

* if you are just a regular user who just wants to use TUDBC without
modifications, then none of these matters to you any way
          o same as GPL to use it for free
          o slightly better than MySQL, because TUDBC has only one set
of released source codes, whereas MySQL paid version is better than
the free version.

* If you make your extensions public, then they belong to TUDBC
          o slightly worse than GPL, because GPL also says you don't
own them, but the public own them.
          o I think for MySQL, if you are a paying customer you
probably won't reveal your modifications. If you do reveal, probably
GPL will apply.

* If you keep the extensions to yourself, then they belong to you
          o slightly better than GPL, because you actually own them
          o  same as MySQL

On 9/13/08, Evert Lammerts <evert.lammerts@gmail.com> wrote:
> Just so you are aware: TUDBC is not published under any of GNU's
>  licenses. The website explains the terms and conditions, which are
>  pretty tight. It does say there are no plans to commercialize TUDBC,
>  but the terms are not at all comforting on that subject.
>
>  I don't recommend building software that depends on it.
>
>
>  On Sat, Sep 13, 2008 at 7:36 AM, Post-No-Reply TUDBC
>  <post-no-reply@tudbc.org> wrote:
>  > I would like to introduce the new exciting TUDBC (Truly Unified
>  > Database Connectivity) to you, which brings both high performance and
>  > high productivity to database access. Currently, it supports
>  >
>  > * 5 programming languages with the same unified coding style for
>  > 1. C# (also any other .NET compliant languages)
>  > 2. Java
>  > 3. PHP (including three flavors: original PHP, Phalanger with ADO.NET
>  > and Quercus with JDBC)
>  > 4. Ruby (including three flavors: original Ruby, IronRuby with
>  > ADO.NET, and JRuby with JDBC).
>  > There is plan to expand to other programming languages, including C,
>  > C++, Perl, Python, etc.
>  > 5. VB.NET
>  >
>  > * All major DBMSes: Access, DB2, Derby, MySQL, Oracle, SQL Server,
>  > plus text CSV and Excel spreadsheets.
>  >
>  > Even though TUDBC works for multiple platforms, the performance is not
>  > sacrificed because it is using a new paradigm and caching technique. One
>  > performance comparison shows that it is close-to-the-best and the best
>  > in various settings.
>  >
>  > On the website (http://www.tudbc.org), you will find interactive live
>  > demos and source codes for all languages. There are also videos of
>  > demos and tutorials, including one that shows you how you can use
>  > TUDBC to create a simple web application in 2 minutes.
>  >
>  > Please share this great news with your colleagues.
>  >
>  > Thanks!
>  >
>  > TUDBC
>  > http://www.tudbc.org
>  >
>
> > --
>  > PHP Database Mailing List (http://www.php.net/)
>  > To unsubscribe, visit: http://www.php.net/unsub.php
>  >
>  >
>

-- 
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

[prev in list] [next in list] [prev in thread] [next in thread]