Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81447
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.46 as permitted sender)
Message-ID: <54CBD723.9050701@gmail.com>
Date: Fri, 30 Jan 2015 11:10:27 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Michael Wallner <mike@php.net>, 
 PHP Internals <internals@lists.php.net>
References: <DDA98D4F-2105-415A-B921-01A622091FA9@php.net>
In-Reply-To: <DDA98D4F-2105-415A-B921-01A622091FA9@php.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC] [DISCUSSION] pecl_http
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> I’ve rewritten the RFC for pecl_http and hopefully addressed most of the things mentioned previously.

Thank you, Michael, this is much better!

I would still like to hear more about 2 extensions, especially about
raphf - it seems to be some framework for handling persistent resources,
but it's not clear why we need persistent resources for HTTP module at
all (who keeps HTTP connections open between requests?) and the code in
the example doesn't show any significant logic there - it just basically
wraps curl functions, so I wonder why we need whole new API in core for
that?

About propro - it says that it improves by-reference access to handler
properties, which may be useful but I don't really see how it relates to
HTTP module either - why would you need by-ref access in this context?
Could you give any example of a common code pattern that was impossible
without it but is enabled with it?

-- 
Stas Malyshev
smalyshev@gmail.com