On 4/13/07, Andrew Hutchings <[EMAIL PROTECTED]> wrote:
Tijnema ! wrote:
> On 4/12/07, Oliver Block <[EMAIL PROTECTED]> wrote:
>> Am Donnerstag, 12. April 2007 06:34 schrieb Andrew Hutchings:
>> > Isn't that what a database is for (e.g. MySQL)?
>>
>> No. - It's that what a symbol table is for.:-)
>>
>> Best Regards,
>>
>> Oliver
>
> You simply could create a table with 2 columns 'key' and 'value', and
> so you could easily store both :)
>
I can see where Oliver is coming from, it would be a lot quicker to do
it that way. But I can imagine there would be problems making something
like that work with all the different types of Apache workers, etc...
without some kind of separate daemon handling it.
Regards
Andrew
I think that will screw up some things, for example when using 2 the
same scripts, on the same apache, but on different locations.
In current ways, the programmer would create a database, and use a
separate table for both scripts. But if these "application variables"
are there, the programmer would use those, but then script 1 & 2 would
both share the same variables, and so that would give a lot of
trouble.
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.
Tijnema
--
Andrew Hutchings - Linux Jedi - http://www.linuxjedi.co.uk/
Windows is the path to the darkside...Windows leads to Blue Screen. Blue
Screen leads to downtime. Downtime leads to suffering...I sense much
Windows in you.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
