- Sort Score
- Result 10 results
- Languages All
Results 41 - 50 of 98 for ASGI (0.06 sec)
-
docs/de/docs/benchmarks.md
Die Hierarchie ist wie folgt: * **Uvicorn**: ein ASGI-Server * **Starlette**: (verwendet Uvicorn) ein Web-Mikroframework * **FastAPI**: (verwendet Starlette) ein API-Mikroframework mit mehreren zusätzlichen Funktionen zum Erstellen von APIs, mit Datenvalidierung, usw.
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Tue Jan 23 16:04:13 UTC 2024 - 3.9K bytes - Viewed (0) -
docs/en/docs/advanced/sub-applications.md
### Technical Details: `root_path` When you mount a sub-application as described above, FastAPI will take care of communicating the mount path for the sub-application using a mechanism from the ASGI specification called a `root_path`. That way, the sub-application will know to use that path prefix for the docs UI.
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 2.9K bytes - Viewed (0) -
docs/ko/docs/deployment/server-workers.md
/// ## 구니콘과 유비콘 워커 **Gunicorn**은 **WSGI 표준**을 주로 사용하는 애플리케이션 서버입니다. 이것은 구니콘이 플라스크와 쟝고와 같은 애플리케이션을 제공할 수 있다는 것을 의미합니다. 구니콘 자체는 최신 **<a href="https://asgi.readthedocs.io/en/latest/" class="external-link" target="_blank">ASGI 표준</a>**을 사용하기 때문에 FastAPI와 호환되지 않습니다. 하지만 구니콘은 **프로세스 관리자**역할을 하고 사용자에게 특정 **워커 프로세스 클래스**를 알려줍니다. 그런 다음 구니콘은 해당 클래스를 사용하여 하나 이상의 **워커 프로세스**를 시작합니다. 그리고 **유비콘**은 **구니콘과 호환되는 워커 클래스**가 있습니다.
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Tue Aug 06 04:48:30 UTC 2024 - 10.2K bytes - Viewed (0) -
docs/fa/docs/advanced/sub-applications.md
### جرئیات فنی : `root_path` هنگامی که یک زیر برنامه را همانطور که در بالا توضیح داده شد متصل می کنید, FastAPI با استفاده از مکانیزمی از مشخصات ASGI به نام `root_path` ارتباط مسیر mount را برای زیر برنامه انجام می دهد. به این ترتیب، زیر برنامه می داند که از آن پیشوند مسیر برای رابط کاربری اسناد (docs UI) استفاده کند.
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 4.1K bytes - Viewed (0) -
docs/es/docs/benchmarks.md
La jerarquía sería: * **Uvicorn**: como servidor ASGI * **Starlette**: (usa Uvicorn) un microframework web * **FastAPI**: (usa Starlette) un microframework API con varias características adicionales para construir APIs, con validación de datos, etc. * **Uvicorn**:
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Wed Feb 07 11:39:50 UTC 2024 - 3.9K bytes - Viewed (0) -
docs/fr/docs/benchmarks.md
La hiérarchie est la suivante : * **Uvicorn** : un serveur ASGI * **Starlette** : (utilise Uvicorn) un micro-framework web * **FastAPI**: (utilise Starlette) un micro-framework pour API disposant de fonctionnalités additionnelles pour la création d'API, avec la validation des données, etc.
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Thu Jul 27 18:49:56 UTC 2023 - 3.9K bytes - Viewed (0) -
docs/de/docs/advanced/events.md
## Technische Details Nur ein technisches Detail für die neugierigen Nerds. 🤓 In der technischen ASGI-Spezifikation ist dies Teil des <a href="https://asgi.readthedocs.io/en/latest/specs/lifespan.html" class="external-link" target="_blank">Lifespan Protokolls</a> und definiert Events namens `startup` und `shutdown`. /// info
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 9.1K bytes - Viewed (0) -
docs/en/docs/benchmarks.md
The simpler the problem solved by the tool, the better performance it will get. And most of the benchmarks don't test the additional features provided by the tool. The hierarchy is like: * **Uvicorn**: an ASGI server * **Starlette**: (uses Uvicorn) a web microframework * **FastAPI**: (uses Starlette) an API microframework with several additional features for building APIs, with data validation, etc. * **Uvicorn**:
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Thu Apr 18 19:53:19 UTC 2024 - 3.4K bytes - Viewed (0) -
docs/pt/docs/advanced/sub-applications.md
### Detalhes Técnicos: `root_path` Quando você monta uma sub-aplicação como descrito acima, o FastAPI se encarrega de comunicar o caminho de montagem para a sub-aplicação usando um mecanismo da especificação ASGI chamado `root_path`. Dessa forma, a sub-aplicação saberá usar esse prefixo de caminho para a interface de documentação.
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 3.2K bytes - Viewed (0) -
docs/de/docs/how-to/custom-request-and-route.md
Ein `Request` hat auch ein `request.receive`, welches eine Funktion ist, die den Hauptteil des Requests empfängt. Das `scope`-`dict` und die `receive`-Funktion sind beide Teil der ASGI-Spezifikation. Und diese beiden Dinge, `scope` und `receive`, werden benötigt, um eine neue `Request`-Instanz zu erstellen.
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 5.2K bytes - Viewed (0)