ID: 19694 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Open +Status: Feedback Bug Type: Feature/Change Request Operating System: N/A PHP Version: 4.2.3 New Comment:
what about using shared memory? http://www.php.net/manual/en/ref.sem.php http://www.php.net/manual/en/ref.shmop.php Previous Comments: ------------------------------------------------------------------------ [2002-10-01 10:19:10] [EMAIL PROTECTED] In "Serversite Javascript" exists the (global) "project" variable. The content of this variable is persistent as long as the Web-Server isn't restarted. This concept is IMHO great for e.g. configuration-variables. Load the configuration once and be done with it until the web-server is restarted. In a project i'm assigned to the configuration is stored in a Oracle-DB. As the configuration must only be parsed once after restarting the web-server the cost of about 2 seconds is no problem at all. In PHP we would have to do this every time a uses requests a page, which is to costly. Currently seems like we have to make an external "Configuration2PHP"-Script which fetches the current configuration and makes a static (PHP-)file out the configuration. (The "application" is "stateless", so it can't be achieved over a session. (->reading the config-reading once per user). And the application is running on many web-servers. With the stateless design the load-balancing is easier as you don't have to "bind" a session to a specific web-server or making a DB-Session or something similar. And you don't have problems with expired/stalled sessions.) "Better(tm)" would be if a concept like a persistent variable is introduced. IMO others would appreciate that too. :-) ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=19694&edit=1
