o >h@s~ddlZddlmZddlmZddlmZmZddlm Z ddl m Z ddl m Z d d ZGd d d ZGd ddeZdS)N) async_to_sync)DEFAULT_CHANNEL_LAYER)aclose_old_connectionsdatabase_sync_to_async) StopConsumer)get_channel_layer)await_many_dispatchcCs6d|vrtd|ddd}|drtd|S)zl Looks at a message, checks it has a sensible type, and returns the handler name for that type. typez(Incoming message has no 'type' attribute._z.Malformed type in message (leading underscore)) ValueErrorreplace startswith)message handler_namerq/var/www/vedio/testing/chatpythonscript.ninositsolution.com/env/lib/python3.10/site-packages/channels/consumer.pyget_handler_name s  rc@s<eZdZdZdZeZddZddZddZ e d d Z d S) AsyncConsumerz Base consumer class. Implements the ASGI application spec, and adds on channel layer management and routing of events to named methods based on their type. Fcs||_t|j|_|jdur"|jIdH|_t|jj|j|_ |j r+t ||_ n||_ z!|jdurCt ||j g|jIdHWdSt |g|jIdHWdStyYYdSw)U Dispatches incoming messages to type-based handlers asynchronously. N)scoperchannel_layer_alias channel_layer new_channel channel_name functoolspartialreceivechannel_receive_syncr base_sendr dispatchr)selfrrsendrrr__call__%s(       zAsyncConsumer.__call__csDt|t|d}|rtIdH||IdHdStd|d)z6 Works out what to do with a message. NNo handler for message type %sr )getattrrrr r#rhandlerrrrr"Cs  zAsyncConsumer.dispatchcs||IdHdSzB Overrideable/callable-by-subclasses send method. Nr!r#rrrrr$NszAsyncConsumer.sendc s.fdd}|_|_tj|dd|S)z Return an ASGI v3 single callable that instantiates a consumer instance per scope. Similar in purpose to Django's as_view(). initkwargs will be used to instantiate the consumer instance. cs"di}||||IdHS)Nrr)rrr$consumercls initkwargsrrapp]sz"AsyncConsumer.as_asgi..appr)updated)consumer_classconsumer_initkwargsrupdate_wrapper)r/r0r1rr.ras_asgiTs  zAsyncConsumer.as_asgiN) __name__ __module__ __qualname____doc__r rrr%r"r$ classmethodr6rrrrrs rc@s(eZdZdZdZeddZddZdS) SyncConsumera Synchronous version of the consumer, which is what we write most of the generic consumers against (for now). Calls handlers in a threadpool and uses CallBouncer to get the send method out to the main event loop. It would have been possible to have "mixed" consumers and auto-detect if a handler was awaitable or not, but that would have made the API for user-called methods very confusing as there'd be two types of each. TcCs0t|t|d}|r||dStd|d)rNr&r )r'rr r(rrrr"vs zSyncConsumer.dispatchcCs||dSr*r+r,rrrr$szSyncConsumer.sendN)r7r8r9r:r rr"r$rrrrr<is    r<)r asgiref.syncrrdbrr exceptionsrlayersrutilsr rrr<rrrrs     N