Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80142
Return-Path: <kontakt@beberlei.de>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 78979 invoked from network); 4 Jan 2015 11:52:24 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 4 Jan 2015 11:52:24 -0000
Authentication-Results: pb1.pair.com header.from=kontakt@beberlei.de; sender-id=unknown
Authentication-Results: pb1.pair.com smtp.mail=kontakt@beberlei.de; spf=permerror; sender-id=unknown
Received-SPF: error (pb1.pair.com: domain beberlei.de from 74.125.82.176 cause and error)
X-PHP-List-Original-Sender: kontakt@beberlei.de
X-Host-Fingerprint: 74.125.82.176 mail-we0-f176.google.com  
Received: from [74.125.82.176] ([74.125.82.176:63213] helo=mail-we0-f176.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id C8/D0-07254-67929A45 for <internals@lists.php.net>; Sun, 04 Jan 2015 06:52:23 -0500
Received: by mail-we0-f176.google.com with SMTP id w61so6406788wes.21
        for <internals@lists.php.net>; Sun, 04 Jan 2015 03:52:18 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:mime-version:date:message-id:subject:from:to
         :content-type;
        bh=y7eVxHBEEvhLCAUAfvh7ZwDxBaKB+tpbXoU4jeFqb7U=;
        b=R2nI216u8vEa07cXGqWpGFtXeCFAeIm9YaiBdZYIFOy+3RyvVKga8+W1XWIqv4NMX6
         MBG/nIzt+QkSdguCo45nSXGNhZLhvlnWfwamHc1nz1VPg9qttTyFJS5Fj1JYOnqI2D0y
         WJXKTlyZEuzH/oKGOt8h7kGtgcxcFtmL0rDemqNLKpIMKg/kzJs8vwT+Tez6EU7tQZlq
         RconTLsEBALg2hb6Ge3niDUyJHAyd6Suqj0K07eht0twl+XOn6YiNwRkGG6HnbugLC43
         5+HaRgBspLY8UQTikwhpcKmyetc0ILER9mNWVWYxFMet3qRcOy2dYbHF0wKZdwGQB7in
         aq3Q==
X-Gm-Message-State: ALoCoQnxJgYYW8/cPn6guNq+MRbni2Fasd7vpLHCoVw1A0SGTzRHotUcfMdBVPGb2l05wf7WrWLT
MIME-Version: 1.0
X-Received: by 10.194.86.135 with SMTP id p7mr168859972wjz.89.1420372337230;
 Sun, 04 Jan 2015 03:52:17 -0800 (PST)
Received: by 10.194.57.73 with HTTP; Sun, 4 Jan 2015 03:52:17 -0800 (PST)
X-Originating-IP: [77.11.123.69]
Date: Sun, 4 Jan 2015 12:52:17 +0100
Message-ID: <CAEPJdu=2oWiSCQOTkO1g5QDs4NrJwd5H14Jks17qrNu7-eQNVg@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0102e4989c1ad2050bd23447
Subject: [RFC] Extension Prepend Files
From: kontakt@beberlei.de (Benjamin Eberlei)

--089e0102e4989c1ad2050bd23447
Content-Type: text/plain; charset=UTF-8

Hey everyone,

I want to open discussion on my RFC to strengthen the ability of extensions
to provide functionality to developers in both C **and** PHP code.

For this extensions can add PHP files to a list of "prepend files" that are
part of every request execution exactly the same way the INI
auto_prepend_file functionality works:

https://wiki.php.net/rfc/extension_prepend_files

I propose implementation details in the RFC, but they are completely up to
discussion. I am even sure there is probably a better way than what I
proposed, because I am not familiar with the code.

greetings
Benjamin

--089e0102e4989c1ad2050bd23447--