Overall, the session function of php can be basically used, which is quite convenient, and saves a lot of it to deal with it yourself.
Trouble things about cookies. The session management of php is still file-based, and the default is in the /tmp directory.
Generate a session file with the same name as the session id, and save the register's
session data. The session has a lifetime, which can be set in /usr/local/lib/.
Efficiency should be considered sloppy, after all, file operations are still required, although it is /tmp. Very much for service
Large applications will generate many session files in /tmp, which is special. . .
What about distributed applications? How many web servers can serve together? There are some tricks, the directory of the session file
It is configurable, and you'll be done by putting all session files into a shared nfs directory. But php
Have you considered the special processing of nfs when generating a unique file? I didn't look at the source code carefully, I guess I'll
Something went wrong, although the chance was very small...
You can make a session keeper damon, and the session data can be stored in the hash table.
Store in memory and complete the session life by using the udp service method (high efficiency, small packet loss rate in lan)
Complete, search, end, and get session variables, so that multiple web servers can share
session information. I have done both the server and client functions. Now the question is how to use the client's functions.
How does the numbers add to php, or how does php support dynamic library function calls? These things are manual
The topics are not detailed, and there are no relevant examples.
BTW: Due to the lack of syntax, the return of php function is easy to cause ambiguity, such as strpos, without
The match returns 0, but the matching position may be 0, fail~...
Trouble things about cookies. The session management of php is still file-based, and the default is in the /tmp directory.
Generate a session file with the same name as the session id, and save the register's
session data. The session has a lifetime, which can be set in /usr/local/lib/.
Efficiency should be considered sloppy, after all, file operations are still required, although it is /tmp. Very much for service
Large applications will generate many session files in /tmp, which is special. . .
What about distributed applications? How many web servers can serve together? There are some tricks, the directory of the session file
It is configurable, and you'll be done by putting all session files into a shared nfs directory. But php
Have you considered the special processing of nfs when generating a unique file? I didn't look at the source code carefully, I guess I'll
Something went wrong, although the chance was very small...
You can make a session keeper damon, and the session data can be stored in the hash table.
Store in memory and complete the session life by using the udp service method (high efficiency, small packet loss rate in lan)
Complete, search, end, and get session variables, so that multiple web servers can share
session information. I have done both the server and client functions. Now the question is how to use the client's functions.
How does the numbers add to php, or how does php support dynamic library function calls? These things are manual
The topics are not detailed, and there are no relevant examples.
BTW: Due to the lack of syntax, the return of php function is easy to cause ambiguity, such as strpos, without
The match returns 0, but the matching position may be 0, fail~...