Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82389
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <54D8BB94.80301@php.net>
References: <DDA98D4F-2105-415A-B921-01A622091FA9@php.net>
	<54D217E7.8030407@php.net>
	<54D2AE91.8090800@gmail.com>
	<54D3271E.2080207@php.net>
	<CAEZPtU65NirGfES1qiic45Ui3qY45X+k370o2BSj3kbwLendjg@mail.gmail.com>
	<54D3CE01.4070903@php.net>
	<54D3D26A.6050405@gmail.com>
	<54D3D51C.8070108@php.net>
	<54D3D6A4.3020908@gmail.com>
	<54D47379.8030409@php.net>
	<54D7E259.4090702@gmail.com>
	<54D8BB94.80301@php.net>
Date: Tue, 10 Feb 2015 12:43:38 -0500
Message-ID: <CAA8DMBu1PvhB5gE_oX4iuUWd3Ha-Ygv9AMMAKxQo74r9akxqQg@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Re: [RFC] [DISCUSSION] pecl_http
From: figureonecpr@gmail.com (Sanford Whiteman)

> Caching connections within the same request and reusing them is not
> spooky, but caching them long term, across requests, across security
> domains, for extended time - is spooky.

This is exactly what reverse proxies like Nginx and the Akamai CDN do:
reuse the connection between the proxy and origin even after the
browser endpoint has disconnected from the proxy.

Like Mike said, it isn't spooky, since the reuse of an HTTP persistent
connection makes no claim about HTTP state.  Heck, Firefox could take
over Chrome's HTTP connections and it would still be to-spec,
regardless of whether they shared credentials. Of course it is
incumbent on the remote server to keep things stateless above the TCP
level, but if it can't do that it shouldn't advertise persistent
connections.

-- Sandy