Search Options

Results per page
Sort
Preferred Languages
Advance

Results 91 - 100 of 144 for osgi (0.02 sec)

  1. 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 Dec 28 07:19:09 UTC 2025
    - Last Modified: Sun Aug 31 09:15:41 UTC 2025
    - 3.5K bytes
    - Viewed (0)
  2. docs/ko/docs/advanced/events.md

    이러한 작업을 별도의 함수로 처리하면 서로 로직이나 변수를 공유하지 않기 때문에 더 어려워집니다. 값들을 전역 변수에 저장하거나 비슷한 트릭을 사용해야 할 수 있습니다.
    
    그렇기 때문에 위에서 설명한 대로 `lifespan`을 사용하는 것이 권장됩니다.
    
    ## 기술적 세부사항
    
    호기심 많은 분들을 위한 기술적인 세부사항입니다. 🤓
    
    ASGI 기술 사양에 따르면, 이는 <a href="https://asgi.readthedocs.io/en/latest/specs/lifespan.html" class="external-link" target="_blank">Lifespan Protocol</a>의 일부이며, `startup`과 `shutdown`이라는 이벤트를 정의합니다.
    
    /// info | 정보
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Sat Oct 11 17:48:49 UTC 2025
    - 9.2K bytes
    - Viewed (0)
  3. docs/de/docs/advanced/behind-a-proxy.md

    In diesen Fällen können Sie <abbr title="Wurzelpfad">`root_path`</abbr> verwenden, um Ihre Anwendung zu konfigurieren.
    
    Der `root_path` ist ein Mechanismus, der von der ASGI-Spezifikation bereitgestellt wird (auf der FastAPI via Starlette aufbaut).
    
    Der `root_path` wird verwendet, um diese speziellen Fälle zu handhaben.
    
    Und er wird auch intern beim Mounten von Unteranwendungen verwendet.
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Wed Dec 17 20:41:43 UTC 2025
    - 18.6K bytes
    - Viewed (0)
  4. docs/zh/docs/advanced/events.md

    在不共享逻辑或变量的不同函数中处理这些逻辑比较困难,因为你需要在全局变量中存储值或使用类似的方式。
    
    因此,推荐使用 `lifespan` 。
    
    ## 技术细节
    
    只是为好奇者提供的技术细节。🤓
    
    在底层,这部分是<a href="https://asgi.readthedocs.io/en/latest/specs/lifespan.html" class="external-link" target="_blank">生命周期协议</a>的一部分,参见 ASGI 技术规范,定义了称为启动(`startup`)和关闭(`shutdown`)的事件。
    
    /// info | 说明
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Sat Oct 11 17:48:49 UTC 2025
    - 7K bytes
    - Viewed (0)
  5. docs/es/docs/advanced/sub-applications.md

    Cuando montas una sub-aplicación como se describe arriba, FastAPI se encargará de comunicar el path de montaje para la sub-aplicación usando un mecanismo de la especificación ASGI llamado `root_path`.
    
    De esa manera, la sub-aplicación sabrá usar ese prefijo de path para la interfaz de documentación.
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Wed Dec 17 20:41:43 UTC 2025
    - 3.2K bytes
    - Viewed (0)
  6. docs/pt/docs/advanced/sub-applications.md

    ### Detalhes Técnicos: `root_path` { #technical-details-root-path }
    
    Quando você monta uma sub-aplicação como descrito acima, o FastAPI se encarrega de comunicar o path 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 path para a interface de documentação.
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Wed Dec 17 20:41:43 UTC 2025
    - 3.3K bytes
    - Viewed (0)
  7. 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 Dec 28 07:19:09 UTC 2025
    - Last Modified: Sat Sep 20 15:10:09 UTC 2025
    - 4K bytes
    - Viewed (0)
  8. docs/en/docs/how-to/custom-request-and-route.md

    A `Request` also has a `request.receive`, that's a function to "receive" the body of the request.
    
    The `scope` `dict` and `receive` function are both part of the ASGI specification.
    
    And those two things, `scope` and `receive`, are what is needed to create a new `Request` instance.
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Wed Dec 10 08:55:32 UTC 2025
    - 4.6K bytes
    - Viewed (0)
  9. docs/ru/docs/how-to/custom-request-and-route.md

    У `Request` также есть `request.receive` — функция для «получения» тела запроса.
    
    И `dict` `scope`, и функция `receive` являются частью спецификации ASGI.
    
    Именно этих двух компонентов — `scope` и `receive` — достаточно, чтобы создать новый экземпляр `Request`.
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Thu Dec 11 21:25:03 UTC 2025
    - 7.2K bytes
    - Viewed (0)
  10. docs/de/docs/how-to/custom-request-and-route.md

    Ein `Request` hat auch ein `request.receive`, welches eine Funktion ist, die den Body des Requests <abbr title="Englisch „receive“">empfängt</abbr>.
    
    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 Dec 28 07:19:09 UTC 2025
    - Last Modified: Wed Dec 10 13:54:34 UTC 2025
    - 5.7K bytes
    - Viewed (0)
Back to top