Re: Re: php feature
| From: | Oliver Block | Date: | Fri, 13 Apr 2007 20:34:10 +0000 |
| Subject: | Re: Re: php feature | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-28798@lists.php.net to get a copy of this message | ||
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