Ë ýk"gâãó@—ddlmZmZGd„de«ZGd„de«Zy)é)ÚAbstractBaseSessionÚBaseSessionManagercó—eZdZdZy)ÚSessionManagerTN)Ú__name__Ú __module__Ú __qualname__Úuse_in_migrations©óúW/var/www/html/djangosite/lib/python3.12/site-packages/django/contrib/sessions/models.pyrrs„ØÑr rcóX—eZdZdZe«Zed„«ZGd„dej«Z y)ÚSessiona Django provides full support for anonymous sessions. The session framework lets you store and retrieve arbitrary data on a per-site-visitor basis. It stores data on the server side and abstracts the sending and receiving of cookies. Cookies contain a session ID -- not the data itself. The Django sessions framework is entirely cookie-based. It does not fall back to putting session IDs in URLs. This is an intentional design decision. Not only does that behavior make URLs ugly, it makes your site vulnerable to session-ID theft via the "Referer" header. For complete documentation on using Sessions in your code, consult the sessions documentation that is shipped with Django (also available on the Django web site). có—ddlm}|S)Nr)Ú SessionStore)Ú#django.contrib.sessions.backends.dbr)Úclsrs r Úget_session_store_classzSession.get_session_store_classs €åDàÐr có—eZdZdZy)ú Session.MetaÚdjango_sessionN)rrr Údb_tabler r r ÚMetar"s„Ø#‰r rN) rrr Ú__doc__rÚobjectsÚ classmethodrrrr r r rrs6„ññ"Ó€Gàñóðô $Ð"×'Ñ'õ$r rN)Ú$django.contrib.sessions.base_sessionrrrrr r r úrs"ðßXôÐ'ôô$Ð!õ$r