On Mon, 5 Sep 2016, at 06:47 PM, Andrea Faulds wrote:
> Hi Michael,
>
> Have you looked into PHP application servers, where the PHP code itself
> acts as the web (or FastCGI) server, and so can keep the whole framework
> etc. initialised in memory between requests?
>
> This is how other (non-PH
On Mon, Sep 5, 2016 at 1:47 PM, Andrea Faulds wrote:
> Hi Michael,
>
> Have you looked into PHP application servers, where the PHP code itself
> acts as the web (or FastCGI) server, and so can keep the whole framework
> etc. initialised in memory between requests?
>
I have - it's what I was refe
Hi Michael,
Have you looked into PHP application servers, where the PHP code itself
acts as the web (or FastCGI) server, and so can keep the whole framework
etc. initialised in memory between requests?
This is how other (non-PHP) web stacks avoid “installing the application
on every single r
On 05.09.2016 at 18:03, Michael Morris wrote:
> Something I was reminded of during the discussion of replacing pear with
> composer that I thought was worthy of it's own thread. Most PHP apps I've
> seen that use composer are
> single point of entry apps - that is there's one front controller, us
Something I was reminded of during the discussion of replacing pear with
composer that I thought was worthy of it's own thread. Most PHP apps I've
seen that use composer are
single point of entry apps - that is there's one front controller, usually
index.php, and .htaccess rules are put in place t
