U 9j@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|krtd|ddd}|dr2td|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)messageZ handler_namer5/tmp/pip-unpacked-wheel-o8d015gg/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|_|jdk rB|jIdH|_t|jj|j|_ |j rTt ||_ n||_ z<|jdk rt ||j g|jIdHnt |g|jIdHWntk rYnXdS)U Dispatches incoming messages to type-based handlers asynchronously. N)scoperchannel_layer_aliasZ channel_layerZ new_channelZ channel_name functoolspartialreceiveZchannel_receive_syncr base_sendr dispatchr)selfrrsendrrr__call__%s(     zAsyncConsumer.__call__csDt|t|d}|r0tIdH||IdHntd|ddS)z6 Works out what to do with a message. NNo handler for message type %sr )getattrrrr rrhandlerrrrrCs  zAsyncConsumer.dispatchcs||IdHdSzB Overrideable/callable-by-subclasses send method. NrrrrrrrNszAsyncConsumer.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. csf}||||IdHS)Nr)rrrZconsumercls initkwargsrrapp]s z"AsyncConsumer.as_asgi..appr)updated)Zconsumer_classZconsumer_initkwargsrupdate_wrapper)r)r*r+rr(ras_asgiTs zAsyncConsumer.as_asgiN) __name__ __module__ __qualname____doc__rrrr rr classmethodr.rrrrrs 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. TcCs2t|t|d}|r||ntd|ddS)rNr!r )r"rr r#rrrrvs zSyncConsumer.dispatchcCs||dSr%r&r'rrrrszSyncConsumer.sendN)r/r0r1r2rrrrrrrrr4is   r4)rZ asgiref.syncrrdbrr exceptionsrZlayersrutilsr rrr4rrrrs     N