Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:74843
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <2C3AA922-B514-45C0-940E-EBF6F931BCE1@googlemail.com>
References: <2C3AA922-B514-45C0-940E-EBF6F931BCE1@googlemail.com>
Date: Wed, 11 Jun 2014 14:03:17 +0200
Message-ID: <CAJWj5+G9unwj0Z2FzE5go5qALTZHERf0gM0CgXioETfY8t_CRg@mail.gmail.com>
To: Kevin Ingwersen <ingwie2000@googlemail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Own webserver, with PHP plus opcache/similar?
From: simonsimcity@gmail.com (Simon Schick)

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 de=
cided I would just try (besides, its the only list I subscribed to).
>
> For an application that I run, I have bumped against apache=E2=80=99s edg=
e: WebSocket support. But the main application is written in PHP, Yii Frame=
work, so I do not want to move away from this - and cant do that very easil=
y 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 exe=
cuted 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 c=
an 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