when app.run(workers=4), works >1, session not eixsts about sanic-session HOT 3 CLOSED

That's probably because you're using the inmemory interface. Each worker will have it's own set of sessions. Ideally, all workers should share the same set of sessions. Try using any of the other storage interfaces instead instead. E.g. Redis

from sanic-session.

Thank you, Omar @omarryhan. That is true.

Session mechanic have few connected parts. You give user special very random number. That is hard or impossible to predict. And on the server side it used as key for user storage with all his/her session data. You need place where you store that data. You definitely can store inside the current process memory, but that means that other processes doesn't have any access to that data. That is why we warn everywhere with comment suitable for testing and development environments.

Best practice use Redis. It is suitable for most cases with default settings. Unless you have more data than free memory on Redis server.

I don't think there is much to add with this ticket. So, I will close it. But if you think that it is important to know to other Chinese-speaking users you can help project by adding some documentation in separated pull request.

from sanic-session.

Thanks，I understood it.

from sanic-session.