Newsgroups: php.doc,php.internals Path: news.php.net Xref: news.php.net php.doc:969384440 php.internals:67757 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 19540 invoked from network); 20 Jun 2013 21:52:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Jun 2013 21:52:10 -0000 Authentication-Results: pb1.pair.com smtp.mail=adam@adamharvey.name; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=adam@adamharvey.name; sender-id=pass Received-SPF: pass (pb1.pair.com: domain adamharvey.name designates 209.85.223.172 as permitted sender) X-PHP-List-Original-Sender: adam@adamharvey.name X-Host-Fingerprint: 209.85.223.172 mail-ie0-f172.google.com Received: from [209.85.223.172] ([209.85.223.172:56991] helo=mail-ie0-f172.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 8F/18-25301-98973C15 for ; Thu, 20 Jun 2013 17:52:10 -0400 Received: by mail-ie0-f172.google.com with SMTP id 16so17995151iea.31 for ; Thu, 20 Jun 2013 14:52:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=adamharvey.name; s=google; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=xvNL/OMyTd+Fpwv20KuI5v4NtU/r0iICmVbmXeAB9kI=; b=oAy0l6803AfkBDM7UC/oElStCTKGv1fp71ZbVWPsyhtUhNFqWaiMElzIABkqyoJd1y YVEBrPwRw5jVK4q5a5J8UuYKIDt77Q4a/a8f2u/OAPhWhc5sowqy5dR0kmVBnE25a76D 5DG6tJAtCMZ/3YjvWnYIvIeL6jAO4oLiDNQvQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding:x-gm-message-state; bh=xvNL/OMyTd+Fpwv20KuI5v4NtU/r0iICmVbmXeAB9kI=; b=P9wyWrB1G0AqIWmNymemZBRiEaBMySz6Z2Iw+GhxBIbcyh393SL7VCuZEBPUDZ7lpX GW7mYoUNeMro9UVxchN7fSnWwtIm0Rd2r/kXAffFKtc5UeMXTyGggzBHNYj0NqB0bsy1 UYtusfAUVNstjww5GnEL7Fu6ImBMsWynuDOsRiXL2oe2qe62yXUFShtXVT2iOplZeax1 hwxL4pjFtta59GeNZvlUsFkzmN67mH/s0+lxGIQ/e1gqM8nTOoGP1DBHiuEy6abVUgIx bCZkx4p/EFDtTOtUi5srQ+ocvbFOgzp3Wfy0FLJa9O9jS/6kbeuR24kVgb0GTTmFHQv3 Aj7g== X-Received: by 10.42.50.202 with SMTP id b10mr4419403icg.7.1371765127168; Thu, 20 Jun 2013 14:52:07 -0700 (PDT) MIME-Version: 1.0 Sender: adam@adamharvey.name Received: by 10.42.169.5 with HTTP; Thu, 20 Jun 2013 14:51:47 -0700 (PDT) In-Reply-To: References: Date: Thu, 20 Jun 2013 14:51:47 -0700 X-Google-Sender-Auth: Mgieu_X1pvAiRgkzQSTvAG1dI6k Message-ID: To: Julien Pauli Cc: PHP Internals , PHP Documentation ML , Dmitry Stogov , Laruence , Hannes Magnusson Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQnNfoYnyYo02DdLnxkgb/sEn5/87BM6EdxasFJl9UXHFWnli7ETpf8DhIb6NkQ5Hj/eU6BU Subject: Re: [PHP-DOC] Re: OPCache documentation From: aharvey@php.net (Adam Harvey) 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 releas= e >> 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 AP= C >> 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 OPCac= he > 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 and 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 th= e 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