No, g
is not an object to hang session data on. g
data is not persisted between requests.
session
gives you a place to store data per specific browser. As a user of your Flask app, using a specific browser, returns for more requests, the session data is carried over across those requests.
g
on the other hand is data shared between different parts of your code base within one request cycle. g
can be set up during before_request
hooks, is still available during the teardown_request
phase and once the request is done and sent out to the client, g
is cleared.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…