per page, with , order by , clip by
Results of 1 - 10 of about 14 for synchronous (0.004 sec.)
非同期サポート — Django 6.1 ドキュメント 12481
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » 非同期サポート ¶ Django has support for writing asynchronous ("async") views, along with an entirely async-enabled request stack if you are running ... cost (see パフォーマンス ), and without the ability to have efficient long-running requests. Many parts of Django provide asynchronous APIs, including the ORM , the cache framework, authentication, sessions, and signals. For other code, the sync_to_async() ... ます ( __init__() でも as_view() でもないことに注意)。 注釈 Django uses inspect.iscoroutinefunction to test if your view is asynchronous or not. If you implement your own method of returning a coroutine, ensure you use inspect.markcoroutinefunction so this fu ... タイプが使えます。 もしこれらを利用したい場合は、代わりに ASGI を使って Django をデプロイする必要があります。 注釈 A fully asynchronous request stack requires async middleware end-to-end. Where a piece of synchronous middleware sits between an ASGI server an ...
https://man.mtool.work/django/6.1/topics/async.html
非同期サポート — Django 6.1 ドキュメント 11220
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » 非同期サポート ¶ Django has support for writing asynchronous ("async") views, along with an entirely async-enabled request stack if you are running ... cost (see パフォーマンス ), and without the ability to have efficient long-running requests. Many parts of Django provide asynchronous APIs, including the ORM , the cache framework, authentication, sessions, and signals. For other code, the sync_to_async() ... ます ( __init__() でも as_view() でもないことに注意)。 注釈 Django uses inspect.iscoroutinefunction to test if your view is asynchronous or not. If you implement your own method of returning a coroutine, ensure you use inspect.markcoroutinefunction so this fu ... タイプが使えます。 もしこれらを利用したい場合は、代わりに ASGI を使って Django をデプロイする必要があります。 注釈 A fully asynchronous request stack requires async middleware end-to-end. Where a piece of synchronous middleware sits between an ASGI server an ...
https://man.mtool.work/django/6.1/topics/async.html
シグナル — Django 6.1 ドキュメント 10905
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » シグナル ¶ Django には "シグナルディスパッチャ" があり、フレームワークの他の場所でアクションが発生したときに、ほかのアプリケーションが通知を受けるの ... toppings , size ): await pizza_done . asend ( sender = self . __class__ , toppings = toppings , size = size ) ... Whether synchronous or asynchronous, receivers will be correctly adapted to whether send() or asend() is used. Synchronous receivers will be c ... alled using sync_to_async() when invoked via asend() . Asynchronous receivers will be called using async_to_sync() when invoked via send() . Similar to the case for middleware , there is a s ... end() or asend() call, the receivers are grouped by whether or not they are async before being called. This means that an asynchronous receiver registered before a synchronous receiver may be executed after the synchronous receiver. In addition, async recei ...
https://man.mtool.work/django/6.1/topics/signals.html
シグナル — Django 6.1 ドキュメント 10905
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » シグナル ¶ Django には "シグナルディスパッチャ" があり、フレームワークの他の場所でアクションが発生したときに、ほかのアプリケーションが通知を受けるの ... toppings , size ): await pizza_done . asend ( sender = self . __class__ , toppings = toppings , size = size ) ... Whether synchronous or asynchronous, receivers will be correctly adapted to whether send() or asend() is used. Synchronous receivers will be c ... alled using sync_to_async() when invoked via asend() . Asynchronous receivers will be called using async_to_sync() when invoked via send() . Similar to the case for middleware , there is a s ... end() or asend() call, the receivers are grouped by whether or not they are async before being called. This means that an asynchronous receiver registered before a synchronous receiver may be executed after the synchronous receiver. In addition, async recei ...
https://man.mtool.work/django/6.1/topics/signals.html
Django 3.0 リリースノート — Django 6.1 ドキュメント 8069
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 3.0 リリースノート ¶ 2019年12月2日 Django 3.0 へようこそ! このリリースノートでは、 バージョン 3.0 の新機能 と、Django 2.2 以前からアップグレー ... under ASGI, however. At this stage async support only applies to the outer ASGI application. Internally everything remains synchronous. Asynchronous middleware, views, etc. are not yet supported. You can, however, use ASGI middleware around Django's applica ... with other ASGI frameworks. There is no need to switch your applications over unless you want to start experimenting with asynchronous code, but we have documentation on deploying with ASGI if you want to learn more. Note that as a side-effect of this chang ... e, Django is now aware of asynchronous event loops and will block you calling code marked as "async unsafe" - such as ORM operations - from an asynchronous conte ...
https://man.mtool.work/django/6.1/releases/3.0.html
Django 3.1 リリースノート — Django 6.1 ドキュメント 8069
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 3.1 リリースノート ¶ August 4, 2020 Django 3.1 へようこそ! このリリースノートでは、 バージョン 3.1 の新機能 と、Django 3.0 以前からアップグレ ... 各バージョン系列の最新リリースのみを公式にサポートし、最新リリースを使用することを 強く推奨 します。 Django 3.1 の新機能 ¶ Asynchronous views and middleware support ¶ Django now supports a fully asynchronous request path, including: Asynchronous views Asynch ... ronous middleware Asynchronous tests and test client To get started with async views, you need to declare a view using async def : async def my_view ( re ... quest ): await asyncio . sleep ( 0.5 ) return HttpResponse ( "Hello, async world!" ) All asynchronous features are supported whether you are running under WSGI or ASGI mode. However, there will be performance penalties using ...
https://man.mtool.work/django/6.1/releases/3.1.html
Django 4.1 リリースノート — Django 6.1 ドキュメント 8069
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 4.1 リリースノート ¶ 2022年8月3日 Django 4.1 へようこそ! このリリースノートでは、 バージョン 4.1 の新機能 と、Django 4.0 以前からアップグレー ... rld!" ) 詳細は 非同期のクラスベース・ビュー を参照してください。 非同期の ORM インターフェース ¶ QuerySet now provides an asynchronous interface for all data access operations. These are named as-per the existing synchronous operations but with an a prefix, ... for example acreate() , aget() , and so on. The new interface allows you to write asynchronous code without needing to wrap ORM operations in sync_to_async() : async for author in Author . objects . filter ( name__sta ... swith = "A" ): book = await author . books . afirst () Note that, at this stage, the underlying database operations remain synchronous, with contributions ongoing to push asynchronous support down into the SQL compiler, and integrate asynchronous database d ...
https://man.mtool.work/django/6.1/releases/4.1.html
Django 3.0 リリースノート — Django 6.1 ドキュメント 8069
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 3.0 リリースノート ¶ 2019年12月2日 Django 3.0 へようこそ! このリリースノートでは、 バージョン 3.0 の新機能 と、Django 2.2 以前からアップグレー ... under ASGI, however. At this stage async support only applies to the outer ASGI application. Internally everything remains synchronous. Asynchronous middleware, views, etc. are not yet supported. You can, however, use ASGI middleware around Django's applica ... with other ASGI frameworks. There is no need to switch your applications over unless you want to start experimenting with asynchronous code, but we have documentation on deploying with ASGI if you want to learn more. Note that as a side-effect of this chang ... e, Django is now aware of asynchronous event loops and will block you calling code marked as "async unsafe" - such as ORM operations - from an asynchronous conte ...
https://man.mtool.work/django/6.1/releases/3.0.html
Django 3.1 リリースノート — Django 6.1 ドキュメント 8069
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 3.1 リリースノート ¶ August 4, 2020 Django 3.1 へようこそ! このリリースノートでは、 バージョン 3.1 の新機能 と、Django 3.0 以前からアップグレ ... 各バージョン系列の最新リリースのみを公式にサポートし、最新リリースを使用することを 強く推奨 します。 Django 3.1 の新機能 ¶ Asynchronous views and middleware support ¶ Django now supports a fully asynchronous request path, including: Asynchronous views Asynch ... ronous middleware Asynchronous tests and test client To get started with async views, you need to declare a view using async def : async def my_view ( re ... quest ): await asyncio . sleep ( 0.5 ) return HttpResponse ( "Hello, async world!" ) All asynchronous features are supported whether you are running under WSGI or ASGI mode. However, there will be performance penalties using ...
https://man.mtool.work/django/6.1/releases/3.1.html
Django 4.1 リリースノート — Django 6.1 ドキュメント 8069
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 4.1 リリースノート ¶ 2022年8月3日 Django 4.1 へようこそ! このリリースノートでは、 バージョン 4.1 の新機能 と、Django 4.0 以前からアップグレー ... rld!" ) 詳細は 非同期のクラスベース・ビュー を参照してください。 非同期の ORM インターフェース ¶ QuerySet now provides an asynchronous interface for all data access operations. These are named as-per the existing synchronous operations but with an a prefix, ... for example acreate() , aget() , and so on. The new interface allows you to write asynchronous code without needing to wrap ORM operations in sync_to_async() : async for author in Author . objects . filter ( name__sta ... swith = "A" ): book = await author . books . afirst () Note that, at this stage, the underlying database operations remain synchronous, with contributions ongoing to push asynchronous support down into the SQL compiler, and integrate asynchronous database d ...
https://man.mtool.work/django/6.1/releases/4.1.html
PREV 1 2 NEXT