Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:27347
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain shininglightpro.com from 217.160.255.148 cause and error)
Message-ID: <45A51BDB.2050902@shininglightpro.com>
Date: Wed, 10 Jan 2007 12:01:15 -0500
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To:  internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: OpenSSL integration
From: shinelight@shininglightpro.com ("Thomas J. Hruska")

I want to access some of the more obscure OpenSSL functions (about 20)
from PHP and would like to contribute what I need access to from OpenSSL
in PHP back to the community.

To that end, I've downloaded the source code for PHP 5.2.0 and started
looking at the C source for the OpenSSL portion to how the functions are
implemented.  My dev platform is Windows and VS.NET 2003 (armed, of
course, with Visual Assist X).

Since this is my first contribution to any open source project (source
code-wise), I will probably need some hand holding (e.g. help with CVS
stuff, first build in my preferred dev environment (VC++ GUI), and
properly using 'diff'/'patch' when I'm done).  However, I am an expert
C/C++ programmer, so there's not much to worry about there - but I do
need to know where the official documentation is for functions like
zend_parse_parameters() and what in the world TSRMLS_CC is (a macro,
obviously, but what it is good for and its historical significance is
usually lost in documentation).

I think that's all I need to know.  The rest I can handle on my own.
And web links to the right portions of the manual (i.e. RTMs) are fine -
I know how to read once I get the right page.  Finding the page is the
tricky part.

(And I'm willing to document undocumented functions as I go along too).

--
Thomas Hruska
CubicleSoft President
Ph: 517-803-4197

http://www.CubicleSoft.com/