Re: Re: upgrading the zlib extension to unicode
| From: | Nuno Lopes | Date: | Thu, 27 Jul 2006 22:19:52 +0000 |
| Subject: | Re: Re: upgrading the zlib extension to unicode | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-25022@lists.php.net to get a copy of this message | ||
Yep. After thoughting about it, I think it is the best way. If the user wants to save the unicode directly (and save BOM, etc), he has functions to handle that.
So, I've just changed the 's' parameters to 'S' (binary only). I left the ob_start handler for Mike since he said he wanted to help with that. The filter code was already upgraded (probably by Sara).
Nuno
----- Original Message -----
So you decide to make the user pass in a binary string explicitly. I suppose that's an approach since it makes them think about what format the binary string should be in before it's compressed. -Andrei On Jul 27, 2006, at 9:41 AM, Nuno Lopes wrote:Nuno Lopes wrote:OK, I think I've completed the upgrade (it now requires a binary string), but I left the ob_gzhandler() function for you ;) NunoHello, So Andrei asked me to upgrade the zlib extension, but I have a few questions I would like to discuss with you:I'd like to collaborate on this. Besides reimplementing the output handler to use the new API, I planned to upgrade it to something similar like http_encoding_api.