> bool psv_register(string var_name, array values, string access_key); > where var_name is variable name, values are array to regieter, > key is access key for the variable.
access key is unique id of an application? If so, I would still prefer the approach with the configuration variable as I if I know your access_key (no matter how complex it may be) I can always access your data. With the configuration variable you would need access to either php.ini or httpd.conf, which typically requires root access. There is one more option, it is more of a hack really, we can use the value of the session.save_path, which should be set on the per application basis anyway. > bool psv_is_registered(string var_name, string access_key); > Return TRUE is var_name is registered with the access_key. Are these PHP userland functions? I believe that the approach with _PERSISTENT or _APPLICATION is better as it is more transparent for the programmer. ... I would also like to add a couple of functions to lock and unlock variables, if possible. psv_lock(string var_name); Locks created on a page would always be destroyed at the end of execution of that page. psv_unlock(string var_name); ... I assume that we will be able to make whole objects persistent, no? -- Best regards, Ivan Ristic, Chief Technology Officer DataGate Network Solutions Ltd. - http://www.datagate.net Tel: +44 8700 119090, Fax: +44 8700 119080 -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
