Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:28801
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.132.241 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=pSARrOBaYfSXRDYQBCgmIQabYTT9uQiOKsz67v/XaOF/IdbSiLz6FJADY3rN42lGqzEDWFDioXe7mbpuJXe70FbKxl8zXJjlhg2svuI9TvjXBaZpWOtLmBT/c3GwtczqO9RayJvIVJyWvVdPkt2BfDyW1JczrU2rtcwezI9Oics=
Message-ID: <d8269d910704131435g39f119a4ge0886d1ca7033fdc@mail.gmail.com>
Date: Fri, 13 Apr 2007 22:35:21 +0100
To: "Oliver Block" <lists@block-online.eu>
Cc: internals@lists.php.net
In-Reply-To: <200704132234.11052.lists@block-online.eu>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <200704112329.l3BNTVnK000581@post.webmailer.de>
	 <36.F7.47553.4513F164@pb1.pair.com>
	 <d8269d910704130646p7ba917f0m3a3b10a53eb3e1a5@mail.gmail.com>
	 <200704132234.11052.lists@block-online.eu>
Subject: Re: [PHP-DEV] Re: php feature
From: tijnema@gmail.com ("Tijnema !")

On 4/13/07, Oliver Block <lists@block-online.eu> wrote:
> Am Freitag, 13. April 2007 15:46 schrieb Tijnema !:
> > I think that will screw up some things, for example when using 2 the
> > same scripts, on the same apache, but on different locations.
>
> It does not screw up things with session variables. The difference between
> session variables and application variables (I would say) is the scope. (Both
> are persistent between several requests.) There are ways to assure that
> requests are served by the same machine if sessions are used (load
> balancers). There is also the way to set up a central storage like you
> already can do with session_set_save_handler().
>
> > Especially because a lot people use shared hosting these days, and
> > that means that they all run on the same apache. and so they would
> > share the same "application variables". So if person a & b both
> > install the same script on a different domain. They would work like 1
> > script, and that just goes wrong.
>
> We two obviously have a different  concept of application variable. As I
> understand it, you would never share applications variables between different
> domains (without the php programmer knowing that). But you are right, if you
> i.e. run a web application on a shared host, you could have a single
> directory served by several different subdomains, e.g. webapp.mydomain1.com,
> webapp.mydomain2.com, webapp.mydomain3.com with all domains mapped to the
> directory htdocs/webapp. But the programmer of the applicaton would have to
> consider this, not php.

But once it is available. "stupid" PHP programmers are gonna use it,
and distribute code using it, and while someone else, who doesn't know
anything about PHP, installs it twice on same host, it does give a lot
trouble.


>
> But as I said earlier, I was more interested in knowing the rationale why this
> feature hasn't been integrated yet, than in demanding it.:) (Right now I have
> no patch, either.)
>
> Best Regards,
>
> Oliver
>
I think it would only give more trouble... and like noted before, it's
a lot of work to integrate it in all apache workers... (not to mention
PHP as CGI...)

Tijnema