How the server maintains the session

After the server creates a session, it will write back the session ID number to the client in the form of a cookie, so that as long as the client's browser is not closed, when accessing the server again, it will go with the session ID number, and the server will use the corresponding session in memory to serve it.

I used this. Follow-up:

page import=""%>listsideburn l=new arraylist();

if("s1")=null)

sl",l);"u","Tourists");

for(int i=0;i I wrote this way to determine if the previous session was empty and clear it if it was empty: Yes. That's pretty much the way it goes, though.

You don't have to determine if a session is empty. Because the session is in the collection. Then it must not be empty.

Follow-up: @page import=""%>listl = new arraylist();

if ("sl") null)

sl", l);else "u"Tourists");boolean x = false;

for (int i = 0; i < i++)for (int i = 0; i < i++)if (x ==false) {

Distributed caching session

Take memcache as an example.

The author uses the memcached-session-manager of the limb surface under Google Code to implement the session caching in a distributed environment, and the performance is not bad after the author's test. Of course, readers can follow similar lines of thought to make their own decisions.

The author uses kryo to do object serialization.

The following needs to be introduced.

lib is introduced below.

contexttag

MemcachedNodes represent memcache nodes, and multiple middle spaces need to be separated (for example: 11211 :11211).

Doesn't iOS have a local cache.

Even if you close the browser, the session is often referred to as the session, but the server's session still exists, the browser's session, because the browser is closed, the browser will empty the session, that is, the server has a session, but the browser does not, and when the time server arrives, it will be automatically released.

The size of the session should have nothing to do with what server it is, it should only have to do with the specific implementation class of the session and what values are stored in the session, generally speaking, the value of a session can be negligible, but the size of the session should be reduced as much as possible, because the number of sessions on the server is very large, even if the size of the session is just a grain of sand, but its number may bury people.

Are you sure the program is okay? 2003 has an application pool that automatically ** resources if the resource usage is exceeded, and then the session is lost.

It is recommended that the server use less session to increase the burden on the server!

Set the session timeout period (default is 20 minutes)4Open the corresponding application pool property on the application pool and change the number of webs to 1 Restart IIS

5.Nest a frame page iframe inside the home page and set the width and height to 0in the loading page inside.

This sentence is added to it to mean that a request is sent to the server every 18 minutes.

Just before the session expires. This way the session never expires.

It's the cookies that are the main problem.