Newsgroups: php.doc,php.internals
Path: news.php.net
Xref: news.php.net php.doc:969384439 php.internals:67756
Return-Path: <theanomaly.is@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 15991 invoked from network); 20 Jun 2013 21:42:15 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 20 Jun 2013 21:42:15 -0000
Authentication-Results: pb1.pair.com smtp.mail=theanomaly.is@gmail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=theanomaly.is@gmail.com; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.171 as permitted sender)
X-PHP-List-Original-Sender: theanomaly.is@gmail.com
X-Host-Fingerprint: 209.85.212.171 mail-wi0-f171.google.com  
Received: from [209.85.212.171] ([209.85.212.171:52498] helo=mail-wi0-f171.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 92/57-25301-53773C15 for <phpdoc@lists.php.net>; Thu, 20 Jun 2013 17:42:14 -0400
Received: by mail-wi0-f171.google.com with SMTP id hj3so25174wib.10
        for <multiple recipients>; Thu, 20 Jun 2013 14:42:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        bh=U/R1TWLOV0xOMLHT/dqaO9WeNDEySjwsFlGAsUBCPNw=;
        b=tjD2RD4wukjubvhQVPpZOPjoqpRj/PuvOmSTmMWV++2XT0v7p80UXGhqVqIgpC+ifo
         +3fgQrnPVD/Yfel7glO1jtcnk5wDywVwrb/DTEnq0jiY33tj3zFF0VQ/OmKE0DMQo7SZ
         BbY/A8c3dEtrUYDBtRDKoM4hmkPlDLXDYB0QuDsZKpRcth41dRVFEOmfZV8QVviquzd+
         my4e8mm3OgWrkD5wc+C4qqfYpoyfvyRRpfygpP1CFnIFnapWsinHh8CiJGSF3XZIvMug
         BLZR0tbCKDIOaQktduBydhC5pltQocQD29DR8iWvc2YCWSGJOVePAVPCLZNv5qUsUzR1
         cZfQ==
MIME-Version: 1.0
X-Received: by 10.194.24.225 with SMTP id x1mr7057099wjf.62.1371764531404;
 Thu, 20 Jun 2013 14:42:11 -0700 (PDT)
Received: by 10.227.60.205 with HTTP; Thu, 20 Jun 2013 14:42:11 -0700 (PDT)
In-Reply-To: <CAMUwpuTVZzLLvqS4aydGY7tUm4f8bJwOfc49HW-h-9dHFKOKow@mail.gmail.com>
References: <CAMUwpuStek+AzAouybK3-gYvK47xWh2dFdjVKLKtaR5iJ1zfhQ@mail.gmail.com>
	<CAMUwpuTVZzLLvqS4aydGY7tUm4f8bJwOfc49HW-h-9dHFKOKow@mail.gmail.com>
Date: Thu, 20 Jun 2013 17:42:11 -0400
Message-ID: <CAL+t6cH7SsY_bQpvqrzWKnXdcqv4wy+OU7wz6A39vMwY=VkYTA@mail.gmail.com>
To: Julien Pauli <jpauli@php.net>
Cc: PHP Internals <internals@lists.php.net>, PHP Documentation ML <phpdoc@lists.php.net>, 
	Dmitry Stogov <dmitry@php.net>, Laruence <laruence@php.net>, 
	Hannes Magnusson <hannes.magnusson@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b5d3c229c25cf04df9cd190
Subject: Re: [PHP-DOC] Re: OPCache documentation
From: theanomaly.is@gmail.com (Sherif Ramadan)

--047d7b5d3c229c25cf04df9cd190
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Jun 20, 2013 at 5:36 PM, Julien Pauli <jpauli@php.net> wrote:

> On Wed, May 15, 2013 at 3:54 PM, Julien Pauli <jpauli@php.net> wrote:
>
>> Hi all,
>>
>> As you know, 5.5 final is coming soon.
>> We are in RC, so mainly stabilizing stuff and preparing the final release
>> for anyone to setup 5.5 on their servers.
>>
>> I see the documentation migration guide has already been commited, that's
>> a good new.
>> I also see that new features we ship in 5.5 are online in the
>> documentation, great !
>>
>> But a crucial feature is missing doc : OPCache.
>>
>> As this feature is a very big step in PHP's life (we finally have a
>> recommanded, bundled opcode cache system, and I'm very proud of this
>> personnaly), I think it is crucial to have a good documentation about it.
>>
>> Has anyone started to write some doc about OPCache ?
>>
>> Another subject is APC. We have its doc on php.net, all right.
>> What I would like is we patch APC doc when 5.5 final gets released, to
>> clearly show our mind about it.
>> That way, any people using 5.5 should be able to read in the doc that APC
>> has support has been interrupted, that APC should never be used together
>> with OPCache, and that OPCache is now the standard recommanded OPCode
>> caching solution for 5.5, 5.4 and 5.3.
>>
>> It is crucial to communicate one this point for our users.
>>
>> Then will come the "User cache" debate
>>
>> Thank you.
>>
>
>
> Up. Could we at least plan such a project ?
> 5.5 is released now. I know we are still having trouble about OpCache
> particulary under Windows. I dont shadow that.
> I would just like we start thinking about writing documentation for
> OPCache features and merge them to our official documentation. If it's
> already planned by someone, just let me know ;-)
>
>
I find it hard to believe this feature made it into 5.5.0 without
a shred of documentation. I would be willing to help, but I actually don't
know much about how opcache works. If anyone is willing to give me a hand I
could draft up some basic FAQ style docs at least so that 5.5.0 users will
have some point of reference.


> Thx.
>
> Julien.Pauli
>

--047d7b5d3c229c25cf04df9cd190--