As most my [PATCH] mails sent to the internals mailing list were ignored (as of today, at least), I'm requesting an access to the PHP CVS, fully aware of what this means.
My contributions (ordered by priority) would include:
- The WDDX extension (http://bugs.php.net/46496)
- The OpenSSL extension (http://bugs.php.net/46127 - a fix for one line missing in PHP 5.3)
- The French documentation (http://bugs.php.net/46073, http://bugs.php.net/46563)
Of course, I intend to continue contributing to these parts of PHP (especially OpenSSL, which is one of the things I use the most, as I'm writing stream servers handling SSL).
My fix for WDDX would allow closing the following forever-waiting bugs:
http://bugs.php.net/45037
http://bugs.php.net/45314
I also intend later (and after some discussions, if anyone has any interest in WDDX) to add a feature to WDDX to provide the ability to stream a packet (create a packet ressource while providing a stream descriptor, send the XML code for the variables when added, then close the packet with an "end of packet" instruction). Providing the reverse process would also have to be done at the same time, using event-based xml parsing.
This would allow memory-efficient creation of large packets.
`
As most my [PATCH] mails sent to the internals mailing list were ignored (as of today, at least), I'm requesting an access to the PHP CVS, fully aware of what this means.
I replied to your mail to internals.
- The OpenSSL extension (http://bugs.php.net/46127 - a fix for one line missing in PHP 5.3)
I replied you on this one earlier this week too.
- The French documentation (http://bugs.php.net/46073, http://bugs.php.net/46563)
Have you contacted the Documentation team?
Cheers,
Hi,
I replied to your mail to internals.
I only have one reply from you which is...
- The OpenSSL extension (http://bugs.php.net/46127 - a fix for one line missing in PHP 5.3)
I replied you on this one earlier this week too.
... this one. You replied to my second reminder for bug #46127 to the
internals mailing list with a promise to look at this patch later. This
is the only reply I got from you for bug I posted on internals (as far
as my mail client can tell).
The patch is still not applied to CVS while it's a pretty simple one
(just one added line to make accepted stream inherit context from their
parent, which is exactly the same that can be found in stream ext).
With the release of PHP 5.2.7 closing by, I would love to see the WDDX
bug (#46496) fixed in time, since it's making our, and other people's
code quite ugly, with stuff like this:
public static function decode($wddx) {
return wddx_deserialize(utf8_encode($wddx));
}
public static function encode($data) {
return utf8_decode(wddx_serialize_value($data));
}
- The French documentation (http://bugs.php.net/46073, http://bugs.php.net/46563)
Have you contacted the Documentation team?
Not yet, as those bugs are ones which I believe to be of lower priority;
still it would be great if they could be fixed too, and I would be happy
to do this. I was planning to start off here, then ask karma from the
doc team later.
Best regards,
Mark
hi,
Hi,
... this one. You replied to my second reminder for bug #46127 to the
internals mailing list with a promise to look at this patch later. This
is the only reply I got from you for bug I posted on internals (as far
as my mail client can tell).The patch is still not applied to CVS while it's a pretty simple one
(just one added line to make accepted stream inherit context from their
parent, which is exactly the same that can be found in stream ext).
Yes, it is not applied, but that does not change anything to my reply.
We are still in the same week (did not see this bug before)...
With the release of PHP 5.2.7 closing by, I would love to see the WDDX
bug (#46496) fixed in time, since it's making our, and other people's
I have nothing to do (not using it) with WDDX, it would be nice to
have an active maintainer for this extension but I can't decide on
what goes on or not, any other developers using it and can valid the
patches (and Mark's request to take the hand on it)?
Cheers,
Pierre
As most my [PATCH] mails sent to the internals mailing list were
ignored (as of today, at least), I'm requesting an access to the PHP
CVS, fully aware of what this means.My contributions (ordered by priority) would include:
- The WDDX extension (http://bugs.php.net/46496)
My fix for WDDX would allow closing the following forever-waiting
bugs:
http://bugs.php.net/45037
http://bugs.php.net/45314I also intend later (and after some discussions, if anyone has any
interest in WDDX) to add a feature to WDDX to provide the ability to
stream a packet (create a packet ressource while providing a stream
descriptor, send the XML code for the variables when added, then
close the packet with an "end of packet" instruction). Providing the
reverse process would also have to be done at the same time, using
event-based xml parsing.
This would allow memory-efficient creation of large packets.
Andrei is the maintainer for the WDDX extension.
Could you give Mark some feedback here?
regards,
Lukas Kahwe Smith
mls@pooteeweet.org
Lukas Kahwe Smith wrote:
I also intend later (and after some discussions, if anyone has any
interest in WDDX) to add a feature to WDDX to provide the ability to
stream a packet (create a packet ressource while providing a stream
descriptor, send the XML code for the variables when added, then close
the packet with an "end of packet" instruction). Providing the reverse
process would also have to be done at the same time, using event-based
xml parsing.
This would allow memory-efficient creation of large packets.Andrei is the maintainer for the WDDX extension.
Could you give Mark some feedback here?
I think that would be a good feature.
-Andrei
Hi,
I believe Andrei's also OK with the solution for this bug. As he said
when one of my colleagues went to a PHP conference (I couldn't this day
for personnal reasons), "English is not the only language".
Having an hardcoded encoding for the "php-side of life" is bad, we could
either make this a php.ini entry (or use a php.ini entry), or stick with
the way most xml functions are done in PHP (only accept UTF-8, that's
what my patch does).
Encoding non utf-8 valid data to base64 (WDDX "binary" type) would be
the best option, the only problem is the overhead of doing this (maybe
people have a need for transmission of binary data, but for now the PHP
WDDX extension isn't able to manage that, it's something else I'd like
to fix, and encoding everything from "ISO-8859-1" is not a solution).
For reference: http://bugs.php.net/46496
So, unless someone have time to bear with me and commit my stuff to WDDX
(I've already started some things for WDDX packet streaming, but anyway
5.2.7 isn't at a point it will accept any new features) I confirm my
request for a CVS account with the ability to edit ext/wddx/ and I hope
to be able to fix bug #46496 before 5.2.7 release.
Best regards,
Mark Karpeles
Le mardi 18 novembre 2008 à 16:23 -0800, Andrei Zmievski a écrit :
Lukas Kahwe Smith wrote:
I also intend later (and after some discussions, if anyone has any
interest in WDDX) to add a feature to WDDX to provide the ability to
stream a packet (create a packet ressource while providing a stream
descriptor, send the XML code for the variables when added, then close
the packet with an "end of packet" instruction). Providing the reverse
process would also have to be done at the same time, using event-based
xml parsing.
This would allow memory-efficient creation of large packets.Andrei is the maintainer for the WDDX extension.
Could you give Mark some feedback here?I think that would be a good feature.
-Andrei
hi Mark,
So, unless someone have time to bear with me and commit my stuff to WDDX
(I've already started some things for WDDX packet streaming, but anyway
5.2.7 isn't at a point it will accept any new features) I confirm my
request for a CVS account with the ability to edit ext/wddx/ and I hope
to be able to fix bug #46496 before 5.2.7 release.
If you still did not get your account, please send me the patch + test
for 5.2, 5.3 and HEAD (at least 5.2 today). I can then commit them
before 5.2.7 next RC (tomorrow).
Cheers,
Pierre