On Mon, 2013-09-30 at 00:25 +0530, Abani Kumar Meher wrote:
> The extension will connect to asterisk on a specified port and write data
> to that port and receive response from asterisk. I am using c/c++ to
> achieve that.
As Rasmus said that should be fine license-wise. I wonder why you write
this in C, not PHP? Is there some more or less complex data format which
has to be en-/decoded? Usually socket communication will make it slow
enough that PHP vs C doesn't matter performance wise.
In general I see two reasons for writing C extensions: Performance and
access to a C library.
Writing pure PHP code instead of a C extension brings benefits in
* deployment (adding PHP scripts to a project is easy, C
extensions needs compilation and loading etc.)
* Simpler development (writing robust PHP code typically is
simpler than robust C code)
* Simpler to get other contributors (Everybody using this library
nows PHP, else they wouldn't use PHP, that's not the case for C
extensions)
If you think there still is benefit we can still add it to PECL. The
process for this looks like this:
1. Provide us with the code from some temporary location so we can
do an initial review to help you and to verify it is a serious
project.
2. If there are no issues request a PECL account
3. If you want to use php.net's svn or git server (which we suggest
as this allows us to do "mass changes" for API updates and
reassign maintainers if original maintainers leave) request that
4. Publish
5. Maintain the code and live a happy life.
johannes
--
PECL development discussion Mailing List (http://pecl.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
