Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:28798 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 17101 invoked by uid 1010); 13 Apr 2007 20:35:32 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 17086 invoked from network); 13 Apr 2007 20:35:32 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Apr 2007 20:35:32 -0000 Authentication-Results: pb1.pair.com header.from=lists@block-online.eu; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lists@block-online.eu; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain block-online.eu from 81.169.146.161 cause and error) X-PHP-List-Original-Sender: lists@block-online.eu X-Host-Fingerprint: 81.169.146.161 mo-p00-ob.rzone.de Solaris 10 (beta) Received: from [81.169.146.161] ([81.169.146.161:15239] helo=mo-p00-ob.rzone.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5F/E3-15016-299EF164 for ; Fri, 13 Apr 2007 16:35:32 -0400 Received: from ollie.block.home (dslb-084-063-170-172.pools.arcor-ip.net [84.63.170.172]) by post.webmailer.de (mrclete mo37) (RZmta 5.5) with ESMTP id G05839j3DK7Abr for ; Fri, 13 Apr 2007 22:35:27 +0200 (MEST) To: internals@lists.php.net Date: Fri, 13 Apr 2007 22:34:10 +0200 User-Agent: KMail/1.7.1 References: <200704112329.l3BNTVnK000581@post.webmailer.de> <36.F7.47553.4513F164@pb1.pair.com> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Message-ID: <200704132234.11052.lists@block-online.eu> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-RZG-AUTH: jsAgD75E4FZRsMYse5W8COLJ40bV42cELvihCND/Uu2brXmKBiVni6RD/38n X-RZG-CLASS-ID: mo00 Subject: Re: [PHP-DEV] Re: php feature From: lists@block-online.eu (Oliver Block) 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 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