Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:59989 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 59242 invoked from network); 16 Apr 2012 08:09:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Apr 2012 08:09:05 -0000 Authentication-Results: pb1.pair.com header.from=kris.craig@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=kris.craig@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.54 as permitted sender) X-PHP-List-Original-Sender: kris.craig@gmail.com X-Host-Fingerprint: 74.125.82.54 mail-wg0-f54.google.com Received: from [74.125.82.54] ([74.125.82.54:55318] helo=mail-wg0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 89/9E-05733-0A3DB8F4 for ; Mon, 16 Apr 2012 04:09:05 -0400 Received: by wgbfg15 with SMTP id fg15so353179wgb.11 for ; Mon, 16 Apr 2012 01:09:02 -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=DWAay0JEgVbZ6CSiIYLfyzbrUCe5XzwoeICzUqQMO4I=; b=eBurgODCsw5TSnMRDh3ROhklQZN7j3sxBnvw493DwLBmgeI9oHGyN0rwc5lQRxwSI3 trem1WTuuvuGCgqKyXEHDz+iullV61G3QvwRFcgQ0FCJKQU3D468ZFAnekKWUkdF5hFY 4JlBGYXRe5eyCWaM62GnnOQFHhtU60Blz0ZE7615wDdHUFu6MXMQcUiiATxt2JOeKUMU 4Nyu1fLbNnnUNWSrObTtQ8QmMziaRdoVgcPK3QXc1SJVtYIQSOlh31vsR18Dg4AkZyBZ k62g84p5TjsH2JXaqpiWwgpizva7d8DyUw4JNu2TabLaAgYiJ3nRwCXNG5w6QUfHXQF5 PT0A== MIME-Version: 1.0 Received: by 10.180.103.35 with SMTP id ft3mr16325205wib.0.1334563741973; Mon, 16 Apr 2012 01:09:01 -0700 (PDT) Received: by 10.223.1.82 with HTTP; Mon, 16 Apr 2012 01:09:01 -0700 (PDT) In-Reply-To: References: <4F876943.8030105@gmail.com> <4F877777.8050806@gmail.com> <4F8782CC.8030205@gmail.com> <4F87C9B0.4080809@gmail.com> <4F8AA9CF.6000003@gmail.com> Date: Mon, 16 Apr 2012 01:09:01 -0700 Message-ID: To: Arvids Godjuks Cc: internals@lists.php.net Content-Type: multipart/alternative; boundary=f46d043bd7e8c53e7204bdc755b7 Subject: Re: [PHP-DEV] [RFC] New .phpp File Type for Pure-Code PHP Scripts From: kris.craig@gmail.com (Kris Craig) --f46d043bd7e8c53e7204bdc755b7 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable On Mon, Apr 16, 2012 at 12:57 AM, Arvids Godjuks wrote: > 16 =C1=D0=D2=C5=CC=D1 2012 =C7. 2:52 =D0=CF=CC=D8=DA=CF=D7=C1=D4=C5=CC=D8= Kris Craig =CE=C1=D0=C9=D3=C1=CC: > > >> >> On Sun, Apr 15, 2012 at 2:30 PM, Arvids Godjuks > > wrote: >> >>> I posted the bellow text in other thread, but i should have it post her= e, >>> so i'm reposting it to this thread. >>> >>> Well, it's time for me to remind about the techique many use (and some >>> frameworks provide it out of the box) - the application file >>> concatination >>> to speed up file loading. >>> Yii framework provides a Yiilite.php file for this, that includes mostl= y >>> used core classes in one big file.that loads much faster and is used fo= r >>> production. Any other framework has user extentions or other type of >>> solutions for this to speed up the application, and it makes really big >>> difference. >>> So there is a good question - how the hell in a MVC framework would i >>> combine my models, controllers, components and other stuff that will >>> definetly be as in .php so in .pphp. And not every file will be cached >>> like >>> that - some will remain as distinct files even in production. >>> >>> The further discussion goes the more questions there is and less answer= s >>> there are. >>> >> >> My response is in the other thread. But you're right, we should move th= e >> discussion back here, so please post your reply here. Thanks! >> >> --Kris >> >> > The Kris response from the "PHP-DEV Digest 13 Apr..." response to my mail > quoted bellow: > > > I'm not quite sure I understand your concern. Are you saying that the > Yii framework wouldn't work with this because .phpp files would be cached > as .php?? If that's the case, what about .phpo? Or, perhaps we should > name the extension .phpf instead, as in "PHP Framework-includable". > > What I'm saying that there is a widely used optimization technique - > concatenate the project files in one big massive chunk, enable an opcode > cache and things speed up big time. Almost any mid sized and above projec= t > ends up doing that in one or the other way. Some even do that on > per-controller basis or otherwise - but the fact is - it's out there. > I just gave an example of the popular framework that has this > out-of-the-box as a feature. And I, for one, do not understand how this > should play with your proposal, because in that state clean source code > ends up with "tainted" source code in one big chunk of machine-generated > striped-out-everything string of epic proportions witch PHP chews with > happy face and damn fast (helps with response times a lot, up to the > tenfold). > What about the per-file approach that's been suggested? Would that work with your framework? The stricter per-stack approach might wind up being better suited for projects that are created from scratch with that architecture in mind. It's common enough that I believe there's a genuine use case for it. If we then had a separate per-file approach designed to accommodate frameworks/libraries that by their nature might be a bit more tangled, I think we could get the best of both worlds with this. --Kris --f46d043bd7e8c53e7204bdc755b7--