You may have different Zoop Application's running which you want to handle session data for separately. A real world example would be if you have one Zoop App for you Admin and another for you Main Site. The Admin may have sessions that last indefinitely while the main site times out after any hour. You can handle different PHP settings using the config.php file to set ini variables.
The examples listed below would allow you to store the session files in the Separate Zoop App tmp folders. This allows PHP's garbage collector to only delete files which relate to the individual session settings so you do not to worry about the conflicting session settings.
//Main Site config.php define("app_session_dir", app_temp_dir . '/sessions'); ini_set('session.cookie_lifetime',3600); ini_set('session.cookie_path','/'); if (!is_dir(app_session_dir)) { mkdir(app_session_dir, 0755); } ini_set('session.save_path', app_session_dir); ini_set('session.gc_maxlifetime', 3600);
If I will integrate this
If I will integrate this formula on my php script site,, will my default or my current setting will not be affected or turn to data loss? Will I guess backup may be the solution,, but I am a bit curious as I do not want to rearrange settings again if I retrieve back my default settings. Mozilla Firefox Review
Will this make any
Will this make any difference if I am on another OS and system? Say for example I am using MAC and on linux?
Regards,
Angel - ipad 2 keyboard designer