On 10/2/06, Andrew Borley <[EMAIL PROTECTED]> wrote:
Hi All, I think it would be good if we could get our first release candidate cut by or during ApacheCon (which is next week!) - do people think that is possible? With this in mind I propose we concentrate on the higher priority stuff, which to my mind is documentation, samples, build requirements (licencing, build files, etc), the PHP extension and the support for a particular spec level. Do people agree with this? Is there some particular functionality/bug fix that should go in? Cheers Andy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Andy, sounds like the right thing to do to me. A couple of points...
I've haven't got back to making the PHP extension as functional as the Ruby and Python extensions yet. The PHP SCA/SDO releases got in the way. But now PHP SCA is out we can use that as the basis for the PHP extension programming model. In theory its not a big deal but to do it properly will take a little thinking. So I'm not sure we can get it done this week:-( I'm currently looking at the details of the PHP SCA implementation so I'll report back when I know how it works. How did the interop stuff go? I lost track of it a little. Did someone offer to repeat your interop tests on the java side. Getting Java/C++ SCA interop the web service level would be cool as we go into milestone 2. When we tried with M! java their binding implementation didn't work for us but now thats been rewritten so would be good to feed back to java about whether it's good this time. S
