Andrei Zmievski wrote:
> Okay, so this doesn't have much to do with Unicode stuff. I think if you
> port it, calling it something other than http_encoding would be a good
> idea, to avoid confusion with other "encoding" settings.
Yeah, of course I thought of php_zlib_*.
Thanks,
--
Michael
--
P
Okay, so this doesn't have much to do with Unicode stuff. I think if
you port it, calling it something other than http_encoding would be a
good idea, to avoid confusion with other "encoding" settings.
-Andrei
On Aug 9, 2006, at 9:13 AM, Michael Wallner wrote:
Andrei Zmievski wrote:
Sorry, r
Andrei Zmievski wrote:
> Sorry, refresh my memory, what are we talking about here?
I was planning to port
http://cvs.php.net/pecl/http/http_encoding_api.c?view=markup
to ext/zlib. It would provide a concise zlib API for PHP and uses a more
performant iterative inflate approach instead of the cur
Sorry, refresh my memory, what are we talking about here?
-A
On Aug 9, 2006, at 3:38 AM, Michael Wallner wrote:
Michael Wallner wrote:
I planned to upgrade it to something similar
like http_encoding_api.
So, are there any objections on that?
Regards,
--
Michael
--
PHP Internals - PHP Runt
Michael Wallner wrote:
> I planned to upgrade it to something similar
> like http_encoding_api.
So, are there any objections on that?
Regards,
--
Michael
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
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 wit
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:
Hello,
So Andrei as
Nuno Lopes wrote:
Hello,
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_encod
Nuno Lopes wrote:
Hello,
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_encod
