������������� �������� ThinkJS �� Hook � Middleware �������������������� ThinkJS ������������������������������� ���� WebSocket � ������� ������������� Hook � Middleware ����� HTTP ���� [2015-10-12 | | | | |-- development.js | | | | `-- production.js | | | |-- hook.js | | | |-- locale | | | | |-- en.js | | | | `-- zh-CN.js ��������������������� ���������� replace_image ����������� hook.js ������������ � �bootstrap ���� common ���� ���������������� ��������hook ���������������� src/common src/common/bootstrap ������

currently used to register additional authentication handlers for conda via the Auth Handlers plugin hook, but may also accom- modate more use cases in the future. Here is an example of how it may be defined available authentication handler called, "test-auth- handler" registered via the aforementioned plugin hook: channel_settings: - channel: https://some.custom/channel auth: test-auth-handler user: my-user-account conda integrate the "hook + entry point" structure by utilizing the Pluggy Python framework. This imple- mentation can be broken down via the following two steps: • Define the hook(s) to be registered

currently used to register additional authentication handlers for conda via the Auth Handlers plugin hook, but may also accom- modate more use cases in the future. Here is an example of how it may be defined available authentication handler called, "test-auth- handler" registered via the aforementioned plugin hook: channel_settings: - channel: https://some.custom/channel auth: test-auth-handler user: my-user-account conda integrate the "hook + entry point" structure by utilizing the Pluggy Python framework. This imple- mentation can be broken down via the following two steps: • Define the hook(s) to be registered

| | | | |-- development.js | | | | `-- production.js | | | |-- hook.js | | | |-- locale | | | | |-- en.js | | | | `-- zh-cn.js register it in the configure file hook.js . tips: bootstrap can only stay in common module. You can place the common config files here. Bear in mind, the route.js, hook.js and locale.js must stay within pathname_suffix: '.html', // the suffix that will be remove when parsing routers hook_on: true, // turns hook on cluster_on: false, //turns cluster on timeout: 120, //120 seconds auto_reload:

currently used to register additional authentication handlers for conda via the Auth Handlers plugin hook, but may also accom- modate more use cases in the future. Here is an example of how it may be defined available authentication handler called, "test-auth- handler" registered via the aforementioned plugin hook: channel_settings: - channel: https://some.custom/channel auth: test-auth-handler user: my-user-account conda integrate the "hook + entry point" structure by utilizing the Pluggy Python framework. This imple- mentation can be broken down via the following two steps: • Define the hook(s) to be registered

currently used to register additional authentication handlers for conda via the Auth Handlers plugin hook, but may also accom- modate more use cases in the future. Here is an example of how it may be defined available authentication handler called, "test-auth- handler" registered via the aforementioned plugin hook: channel_settings: - channel: https://some.custom/channel auth: test-auth-handler user: my-user-account conda integrate the "hook + entry point" structure by utilizing the Pluggy Python framework. This imple- mentation can be broken down via the following two steps: • Define the hook(s) to be registered

want to use a hook: async('math.modf', 2.5, hook='hooks.print_result') # hooks.py def print_result(task): print(task.result) async() can take the following optional keyword arguments: hook The function This enables you to use these keywords for your function call: # Async options in a dict opts = {'hook': 'hooks.print_result', 'group': 'math', 'timeout': 30} async('math.modf', 2.5, q_options=opts) django-redis , you can configure Django Q to use its connection pool. 1.2.5 Reference async(func, *args, hook=None, group=None, timeout=None, save=None, sync=False, redis=None, q_options=None, **kwargs) Puts

conda integrate the "hook + entry point" structure by utilizing the Pluggy Python framework. This imple- mentation can be broken down via the following two steps: • Define the hook(s) to be registered registered • Register the plugin under the conda entrypoint namespace Hook Below is an example of a very basic plugin "hook": Listing 1: my_plugin.py import conda.plugins @conda.plugins.hookimpl def conda_subcommands(): subprocess_call to use text=True to avoid manual encod- ing/decoding. (#13240) • Add a new plugin hook giving plugin authors the ability to define new settings. (#13554) • Optimize module imports to speed

conda integrate the "hook + entry point" structure by utilizing the Pluggy Python framework. This imple- mentation can be broken down via the following two steps: • Define the hook(s) to be registered registered • Register the plugin under the conda entrypoint namespace Hook Below is an example of a very basic plugin "hook": Listing 1: my_plugin.py import conda.plugins @conda.plugins.hookimpl def conda_subcommands(): subprocess_call to use text=True to avoid manual encod- ing/decoding. (#13240) • Add a new plugin hook giving plugin authors the ability to define new settings. (#13554) • Optimize module imports to speed

currently used to register additional authentication handlers for conda via the Auth Handlers plugin hook, but may also accom- modate more use cases in the future. Here is an example of how it may be defined available authentication handler called, "test-auth- handler" registered via the aforementioned plugin hook: channel_settings: - channel: https://some.custom/channel auth: test-auth-handler user: my-user-account conda integrate the "hook + entry point" structure by utilizing the Pluggy Python framework. This imple- mentation can be broken down via the following two steps: • Define the hook(s) to be registered