Newsgroups: php.doc,php.internals Path: news.php.net Xref: news.php.net php.doc:969384447 php.internals:67767 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 71889 invoked from network); 21 Jun 2013 06:05:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Jun 2013 06:05:34 -0000 Authentication-Results: pb1.pair.com smtp.mail=dmitry@zend.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=dmitry@zend.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain zend.com from 209.85.128.181 cause and error) X-PHP-List-Original-Sender: dmitry@zend.com X-Host-Fingerprint: 209.85.128.181 mail-ve0-f181.google.com Received: from [209.85.128.181] ([209.85.128.181:41882] helo=mail-ve0-f181.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C9/20-05022-C2DE3C15 for ; Fri, 21 Jun 2013 02:05:34 -0400 Received: by mail-ve0-f181.google.com with SMTP id db10so5811025veb.26 for ; Thu, 20 Jun 2013 23:05:30 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=vH/hvTEVjfCAcBXOfcEbGlhB0vMaXS0bPWtuFb1IQLA=; b=m7umFp41YAFcDsvSpAyBOp9Bl5DF3308iZLUX2qo61Ctl7qQEHfzC6RZjeB7qTglnk WSioRva57TdRktIjE1+6AhCm4c1erZ2IiiSovrhjqT1TARlLgULDDOtXIvMMz3P1/EY1 T2wnTlu4E1XWOml0UQA6KhCYev+9aUZbgH9M1rkkuFsj+d8BEvM5EYSpYViNai71DTAC trgraigl+SxhGj3aZvdpxJD7e9xBW4QcS/4Ahcq4a7518IEhrhgCmkXyeI8ak++tvfcB /G0+kZ37ImJFyifAJaljm5BAqYKCs20MjntuzAo95QSg9sd+zO3rVy1R+f8Q9OTQO05k k4MQ== MIME-Version: 1.0 X-Received: by 10.58.32.138 with SMTP id j10mr4918075vei.64.1371794730372; Thu, 20 Jun 2013 23:05:30 -0700 (PDT) Received: by 10.52.73.228 with HTTP; Thu, 20 Jun 2013 23:05:30 -0700 (PDT) In-Reply-To: References: Date: Fri, 21 Jun 2013 10:05:30 +0400 Message-ID: To: Adam Harvey Cc: Julien Pauli , PHP Internals , PHP Documentation ML , Dmitry Stogov , Laruence , Hannes Magnusson Content-Type: multipart/alternative; boundary=047d7b417e199be30704dfa3d9ad X-Gm-Message-State: ALoCoQl4k1hGWBzhATE3Y5VHUHUyGYCAuqXrhw5/uLjMJkUxaI520K2yR75L8x+a7BtHMqpLLMexdr5acui8zeQE4fFQfQAeMbg7tlc+tGKHD5fGaiQRWMQSdcZZY5gUc651ECMXFGoq Subject: Re: [PHP-DOC] Re: OPCache documentation From: dmitry@zend.com (Dmitry Stogov) --047d7b417e199be30704dfa3d9ad Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Adam, Thank you for taking this work. In case you have any questions, I'll glad to help. Thanks. Dmitry. On Fri, Jun 21, 2013 at 1:51 AM, Adam Harvey wrote: > On 20 June 2013 14:36, Julien Pauli wrote: > > On Wed, May 15, 2013 at 3:54 PM, Julien Pauli 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 togeth= er > >> 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'm working on some basic opcache documentation as we speak, since it > was pointed out on #php.doc. That said, mostly what I'm doing for now > is adapting the README in ext/opcache and documenting opcache_reset() > and opcache_invalidate() =E2=80=94 some additional theory of operating an= d > setup documentation would be very welcome. > > There should be something to look at in SVN in the next hour or so. > > My apologies =E2=80=94 I wrote the first draft of the migration guide in = the > mid alpha stage (ie before opcache was merged) of 5.5 with the > intention of going back to flesh it out before the final release, but > time has been a bit of an issue. Turns out moving halfway across the > world is a real time sink. > > Adam > --047d7b417e199be30704dfa3d9ad--