Re: [phplib] The change to PEAR... From: Alex Black (enigma <email protected>)
Date: 01/18/01

I'd love to see that happen.

But I do not think it will, certainly not under the Zend banner: I have seen
Zeev _repeatedly_ kill that idea on php.dev

though, for the moment, I'm happy enough the APC
(http://apc.communityconnect.com/)

:)

_alex 

--
Alex Black, Head Monkey
enigma <email protected>

The Turing Studio, Inc.
http://www.turingstudio.com

vox+510.666.0074
fax+510.666.0093

Saul Zaentz Film Center
2600 Tenth St Suite 433
Berkeley, CA 94710-2522

> From: "Chris Johnson" <chris <email protected>>
> Reply-To: <chris <email protected>>
> Date: Thu, 18 Jan 2001 18:36:24 -0600
> To: <phplib <email protected>>
> Subject: RE: [phplib] The change to PEAR...
> 
> A PHP application server as you describe is a great idea.  I'm only
> surprised because I figured that the folks who developed mod_php had
> already done most of that -- i.e. the Apache instance (Unix process) is
> much longer lived, and mod_php could certainly have data stores which
> persist across pages.  Somehow, I thought all along mod_php was smart
> enough keep connections in such a place, and with PHP4, sessions as
> well.
> 
> I guess not!  :-)
> 
> So...how soon can we have this PHP app-server, and how can I help make
> it happen?
> 
> ..chris
> 
>> -----Original Message-----
>> From: Kristian Köhntopp [mailto:kk <email protected>]
> 
>> Imagine a single PHP server process, independent of a web
>> server. If you
>> request a PHP page from a web server, a stub server API would
>> gather all
>> needed request parameters, ship them to the PHP server process, that
>> process would produce the result page, and ship it back to
>> the web server
>> process. That process would send the generated page back to
>> your browser.
> 
>> But our PHP server could not have a special array
>> called $SHARED[], which is NOT cleared at the end of a
>> request and which
>> is not private to a single request thread but shared by all requests.
>> Because these variables are part of a single Unix process,
>> and that process
>> does not end, you could even keep ressources in this array,
>> like database
>> connections, image handles or open files. This finally allows for
>> proper ressource pooling and usage instead of lame pconnects().
>> 
>> One would wish for another array $SESSION[], which is just a
>> shorthand for
>> $SHARED["sess_".SID][]. Using the $SESSION[] array, you'd
>> simply store things
>> you wanted to remember in that array and they would stick around on a
>> per session basis. No page_open(), no session_start() needed.
>> 
>> Simple, compatible and easy to understand. And much more
>> powerful than any
>> session management library could ever be.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: phplib-unsubscribe <email protected>
> For additional commands, e-mail: phplib-help <email protected>
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: phplib-unsubscribe <email protected>
For additional commands, e-mail: phplib-help <email protected>