Re: Own webserver, with PHP plus opcache/similar?

From: Date: Wed, 11 Jun 2014 03:03:17 +0000
Subject: Re: Own webserver, with PHP plus opcache/similar?
References: 1 2  Groups: php.internals 
Request: Send a blank email to internals+get-74837@lists.php.net to get a copy of this message
Am 11.06.2014 um 04:16 schrieb Tom Samplonius <tom@samplonius.org>: > > On Jun 10, 2014, at 5:03 PM, Kevin Ingwersen <ingwie2000@googlemail.com> wrote: > >> Hey. >> >> I am not particulary sure if this is the right list to ask this, but I decided I would just >> try (besides, its the only list I subscribed to). >> >> For an application that I run, I have bumped against apache’s edge: WebSocket support. >> But the main application is written in PHP, Yii Framework, so I do not want to move away from this - >> and cant do that very easily either. So I was thinking about writing my own webserver, maybe in >> nodejs or the like, but also take best advantage of PHP. > > ... > > You may want to look at how this is done in Phabricator (http://phabricator.org/). Besides, > overall being a very interesting piece of modern PHP code, Phabricator uses a very simple node.js > server for websockets. The PHP code sends messages to node.js, and node.js distributes them to any > listening users. Phabricator is released under the Apache license, so you can cherry pick code > easily. > > > > Tom I can pretty much imagine how this works, I am trying to obtain some osurce at the moment. But what I was really interested in, is how to make PHP use previously ran scripts. Like I run them once, and part of it, like classes and such, stay in memory, instead of having to „recompile“ the script. I thought this is doen using OPcache… Any way I can take advantage of somethin glike this?

« previous php.internals (#74837) next »