Re: [PHP4BETA] What is ext/lcg/lcg.c?

On Sun, Aug 29, 1999 at 11:32:36PM +0200, Zeev Suraski wrote: > At 22:30 29/08/99 , Sascha Schumann wrote: > > > Well, I'm not sure what we're waiting for exactly, to be honest. Do you > > > have an idea on how to implement this shared pool of objects in a platform > > > independent (read: works under both UNIX and Win32) way? > > > > Well, I'm not sure what you mean with "objects." > > > > As Rasmus noted, we will need some flexible mechanism to > > provide modules with additional capabilities (i.e. on > > process/thread startup/shutdown events already exists, I > > needed on server startup/shutdown events). These fit well > > into the existing zend_module_entry structure. > > > > Stig mentioned portability problems wrt server capabilities, > > i.e. > > > > #define SAPI_PRE_FORK_START_HOOK > > #define SAPI_PROCESS_START_HOOK > > > > which allow modules to adapt their behaviour to possible > > configurations. > > > > I don't know what new features Apache 2 will introduce in > > this area, but we should take that into account. Maybe > > someone has pointers to papers about the new design of > > Apache. > > We can't really rely on Apache though. We must use features available in > all major servers. Let me rephrase the paragraph (notice the lines above the last paragrapth about compatibility between various server interfaces): Either we go the - lowest-common-determinator route Advantage: Everything runs everywhere Disadvantage: Special services are hard to implement if not all "major" servers support it. For example, server A and B support a special feature, but major server C does not. - provide-hooks-as-necessary route Advantage: Special services can determine whether they will work on the target platform. Disadvantage: Not everything runs everywhere -- Regards, Sascha Schumann Consultant