Re: Commercial Extensions

PHP support dynamically loading extensions. Most of the extensions bundled with PHP can be compiled as a shared extension. ie. ./configure --with-mysql=shared would create a mysql.so file that can then be loaded from a PHP script by using dl('mysql.so') or you can preload it by adding the line: "extension=mysql.so" to you php.ini file. Now, to ship a commercial extension for PHP, simply ship a shared library. Developing one of these has gotten much easier. Read the README.EXT_SKEL in the PHP distribution tarball and follow the instructions there. But, for the record, I believe you are better off shipping source and if you wish to somehow restrict users do so using a license which spells out the rights your customers are buying. This also allows you to support an infinite number of different platforms instead of requiring that you build your shared library on a hundred different types of systems. And you are going to have help debugging problems, enhancing your product, etc... -Rasmus On Tue, 7 Nov 2000, Blake Schwendiman wrote: > Has there been any discussion of how a company should provide extensions to > PHP if the company prefers not to release their source code? I have had a > few discussions recently with some companies who have Java and COM versions > of their products available for JSP and ASP web developers. Many people in > these companies are interested in the PHP developer market, but are unsure > how to do so. > > I realize that PHP supports both COM and Java, but there is an interest in > providing native C/C++ and PHP support. What options does such a company > have? > > Sincerely, > Blake Schwendiman > Intechra LLC > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net > For additional commands, e-mail: php-dev-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net >