Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:67753 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 11108 invoked from network); 20 Jun 2013 21:36:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Jun 2013 21:36:49 -0000 Authentication-Results: pb1.pair.com smtp.mail=julienpauli@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=julienpauli@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.42 as permitted sender) X-PHP-List-Original-Sender: julienpauli@gmail.com X-Host-Fingerprint: 209.85.212.42 mail-vb0-f42.google.com Received: from [209.85.212.42] ([209.85.212.42:59752] helo=mail-vb0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B5/36-25301-0F573C15 for ; Thu, 20 Jun 2013 17:36:49 -0400 Received: by mail-vb0-f42.google.com with SMTP id i3so5126367vbh.15 for ; Thu, 20 Jun 2013 14:36:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=z9iCStE9sycPP4rZm2AnHmrEfFYKuccx79luB39FTXc=; b=BVa1Z1WQeH69QRzKyBygYMb3q8BS9BOUf9IIYmh+s4trA59cZGVjyltGj2Q1cB7T55 XKXZi8akgQGbK4pO/iRvDOjwpx4+Dz1arXOb8VvWO72XdP3HFFF/9YrUTaZxMJ8oVSNE +Ubt4WsUji11TBgZNceRPrY0tbms3h81WNJmfFEo4G9kRdF0XSBv5T9V+2KEd+qUfTzh 8lgvjhEl/Bqh+EVLquh85CITELJRT20W/L34AstjYrV6/BtmHwHoh73vSAxjNXKlhKkP Ka0VufHcCYpWIVN7G8oM6Ya7LgIKltl7AiKFyy+W5nSO4ICvrWLfC8n5MjOOSFeoxbnz vd8w== X-Received: by 10.220.250.147 with SMTP id mo19mr3865701vcb.79.1371764205981; Thu, 20 Jun 2013 14:36:45 -0700 (PDT) MIME-Version: 1.0 Sender: julienpauli@gmail.com Received: by 10.220.188.73 with HTTP; Thu, 20 Jun 2013 14:36:05 -0700 (PDT) In-Reply-To: References: Date: Thu, 20 Jun 2013 23:36:05 +0200 X-Google-Sender-Auth: wAO4GSJdAH8TjKNesqQ1J9FrAjg Message-ID: To: PHP Internals , PHP Documentation ML , Dmitry Stogov , Laruence , Hannes Magnusson Content-Type: multipart/alternative; boundary=089e013cb73e36a22b04df9cbe06 Subject: Re: OPCache documentation From: jpauli@php.net (Julien Pauli) --089e013cb73e36a22b04df9cbe06 Content-Type: text/plain; charset=ISO-8859-1 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 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 ;-) Thx. Julien.Pauli --089e013cb73e36a22b04df9cbe06--