When your parent starts dating
this is because a request is reading and locking the session file to prevent corruption.
I don't know about other enviroments, but in Windows XP, if you edit a document and set it to be UTF-8, the editor (notepad for exapmle) inserts two invisible bytes at the beginning of the file (they read FF FE in hex for me).is called or when a session auto starts, PHP will call the open and read session save handlers.These will either be a built-in save handler provided by default or by PHP extensions (such as SQLite or Memcached); or can be custom handler as defined by .The read callback will retrieve any existing session data (stored in a special serialized format) and will be unserialized and used to automatically populate the $_SESSION superglobal when the read callback returns the saved session data back to PHP session handling.To use a named session, call When you have an import script that takes long to execute, the browser seem to lock up and you cannot access the website anymore.I suppose this happens so Windows can identify the file as UTF-8.
Since these two bytes are placed before anything else in the file, including tags, when you execute the php script, they get outputed to the browser (even tough they won't be shown in the source of the result document, they're there!
) before your php code gets a chance to run anything. from the same user) then the 2nd script will not finish its call to session_start() until the first script finishes execution.
This effectively cripples functions like session_start() ($_COOKIE to be exact). If you have scripts that run for more than a second and users may be making more than 1 request at a time then it is worth calling session_write_close() as soon as you've finished writing session data.
The solution is to save the php file in a different encoding, or to manually remove them (I prefer the former). A note about session_start(), custom handlers and database foreign key constraints, which I think may be of some use...
We know that if we want our sessions into a database table (rather than the default storage), we can refer to session_set_save_handler(...) to get them there.
Note that session_set_save_handler must (obviously) be called before session_start(), but let me get to the point...