On 25 Oct 2013, at 12:51, Nibin V M nibi...@gmail.com wrote:
Thank you for the quick response Stuart...one more doubt..at
http://php.net/manual/en/features.persistent-connections.php they states
=
This means that when the same client makes a second request to the server, it
may
On 25 Oct 2013, at 11:10, Nibin V M nibi...@gmail.com wrote:
I have been reading docs and many are telling that persistent connections
are kept open indefinitely. But I found in PHP docs that it will not close
after script execution like requesting a page; so should it close after
the
no, not at all... but there is a time and a place, and i don't think you
should use pconnect just because you don't want to an include at the top of
every page.
- Original Message -
From: John Hicks [EMAIL PROTECTED]
To: php [EMAIL PROTECTED]
Sent: Tuesday, March 25, 2003 5:11 PM
Subject:
no, not at all... but there is a time and a place, and i don't think you
should use pconnect just because you don't want to an include at the top
of
every page.
You still have to call pconnect() on every page if you use it. It doesn't
leave it open for other requests, it leaves it open within
Frank Joerdens wrote:
On Fri, Jan 26, 2001 at 11:01:14AM +, Nuno Silva wrote:
[ . . . ]
i ran across this transaction problem vs. persistent conn in pgsql some time ago.
I found two workaround methods:
- don't use persistent conn's :-) or;
- start every conn with the usual
Frank Joerdens wrote:
On Thu, Jan 25, 2001 at 05:10:54PM -0300, Martin A. Marques wrote:
[ . . . ]
OK, lets see if we can understand what each other is saying (maybe I'm not
getting your point here).
Lets say browser A connects to the apache server, to a page using php code.
Lets say
On Fri, Jan 26, 2001 at 11:01:14AM +, Nuno Silva wrote:
[ . . . ]
i ran across this transaction problem vs. persistent conn in pgsql some time ago.
I found two workaround methods:
- don't use persistent conn's :-) or;
- start every conn with the usual pg_pconnect and then query a
on 1/25/01 11:49 AM, Frank Joerdens at [EMAIL PROTECTED] wrote:
On Thu, Jan 25, 2001 at 04:04:24PM -0300, Martin A. Marques wrote:
[ . . . ]
Of course. But the persistent connection are not working as the manuals say
they should work.
It appears this riddle has been solved: From a post by
On Thu, Jan 25, 2001 at 11:18:49AM -0300, Martin A. Marques wrote:
[ . . . ]
No, and thats why in the postgres list we talked about persistent connections
not having much benefits. That is because the connection is persistent to the
httpd child that called it and not to all.
Well, yes, but
El Jue 25 Ene 2001 14:34, Frank Joerdens escribi:
On Thu, Jan 25, 2001 at 11:18:49AM -0300, Martin A. Marques wrote:
[ . . . ]
No, and thats why in the postgres list we talked about persistent
connections not having much benefits. That is because the connection is
persistent to the httpd
El Jue 25 Ene 2001 16:49, Frank Joerdens escribi:
On Thu, Jan 25, 2001 at 04:04:24PM -0300, Martin A. Marques wrote:
[ . . . ]
Of course. But the persistent connection are not working as the manuals
say they should work.
It appears this riddle has been solved: From a post by Adam Lang on
On Thu, Jan 25, 2001 at 05:10:54PM -0300, Martin A. Marques wrote:
[ . . . ]
OK, lets see if we can understand what each other is saying (maybe I'm not
getting your point here).
Lets say browser A connects to the apache server, to a page using php code.
Lets say the code is OK (no bugs).
12 matches
Mail list logo
