ó
    5js  ã                   óP   • S r SrSSKJr  SSKJr  SSKJr  SSKJ	r	J
r
  SSKJrJr  g	)
aÞ  Session layer.

Accessing the Data Platform to retrieve content requires your application to authenticate and manage
connection semantics to keep the user session live. LSEG Data Libraries provide this managed access through an
interface called a session. The session is the interface to the data platform and is responsible for defining
authentication details, managing connection resources, and implementing the necessary protocol to communicate with
the data platform. Depending on the access point your application uses to connect to the platform, it can choose from
one of the session implementations to initiate the connection. For the creation phase, all session implementations
expose the same API and behave in the same way.
)Ú
DefinitionÚSessionÚset_defaultÚget_defaultÚ	EventCodeÚdesktopÚplatformé   )r   )r   )r   )r   r   é   )r   r   N)Ú__doc__Ú__all__Ú!_core.session._session_definitionr   Ú_core.session._sessionr   Ú_core.session.event_coder   Ú&_core.session._default_session_managerr   r   Ú r   r   © ó    ÚY/root/lseg-credit/backend/venv/lib/python3.13/site-packages/lseg/data/session/__init__.pyÚ<module>r      s%   ðñ	ð€õ ;Ý ,Ý 0ß Mß Ð r   