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

On Wed, Jun 11, 2014 at 2:03 AM, 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. > > What I mean is, that I read somewhere, that php-fpm, or something similar?, can stay open as a > background process and cache scripts, so they are executed faster. > > Again, I only skimmed over an article, but sadly do not have access to my browser history at th > emoment - and will not for a bunch of weeks - so I can not get back there. > > What would you recommend for this? I want to max out the speed of my PHP execution time. > > Kind regards, > Ingwie. > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > Hi, Ingwie Yesterday, I stumbled over something that might be helpful for your - maybe not ;) I found out, that there are projects on the way out, that let you store stuff accross requests. I don't know how production-ready these ideas are, but you can use them. They work in development ;) A complete redesigned server in PHP only. Worth a view, I think ... they borowed much from Java. That's also how I found that one. http://www.appserver.io/ React is a project, that should let PHP work as Node.JS works. http://reactphp.org/ I think this is the reason, why you think of using Node.JS at all, right? Having one process, that has some resources in memory and that handles all incoming requests - not an engine that has to be turned on and turns off after each request. Bye Simon