<?xml version="1.0" encoding="UTF-8"?>
<metadata>
  <groupId>org.codelibs.fess</groupId>
  <artifactId>fess-crawler-smbj</artifactId>
  <versioning>
    <latest>14.15.0</latest>
    <release>14.15.0</release>
    <versions>
      <version>14.14.0</version>
      <version>14.15.0</version>
    </versions>
    <lastUpdated>20240526053206</lastUpdated>
  </versioning>

iolationDescr":"NO STOP/STAND AM","Fine":93,"Latitude":99999,"Longitude":99999} {"Ticket":1106506413,"IssueData":"2015-12-22T00:00:00","IssueTime":"1100","RPState":"CA","PlateExpiry":"201701","Make":"NISS","BodyStyle":"PA","Color":"SI","Location":"1159 HUNTLEY DR","Route":"2A75","Agency":1,"ViolationCode":"8069AA","ViolationDescr":"NO STOP/STAND AM","Fine":93,"Latitude":99999,"Longitude":99999}...

Das Erste, was auffällt, ist, dass wir eine asynchrone Funktion mit `yield` definieren. Das ist sehr ähnlich zu Abhängigkeiten mit `yield`.

{* ../../docs_src/events/tutorial003_py310.py hl[14:19] *}

Der erste Teil der Funktion, vor dem `yield`, wird ausgeführt **bevor** die Anwendung startet.

Und der Teil nach `yield` wird ausgeführt, **nachdem** die Anwendung beendet ist.

### Lifespan function { #lifespan-function }

The first thing to notice, is that we are defining an async function with `yield`. This is very similar to Dependencies with `yield`.

{* ../../docs_src/events/tutorial003_py310.py hl[14:19] *}

The first part of the function, before the `yield`, will be executed **before** the application starts.

And the part after the `yield` will be executed **after** the application has finished.

### Função lifespan { #lifespan-function }

A primeira coisa a notar é que estamos definindo uma função assíncrona com `yield`. Isso é muito semelhante a Dependências com `yield`.

{* ../../docs_src/events/tutorial003_py310.py hl[14:19] *}

A primeira parte da função, antes do `yield`, será executada **antes** de a aplicação iniciar.

E a parte posterior ao `yield` será executada **depois** de a aplicação ter terminado.

        C = HH(C, D, A, B, X[4], 11);
        B = HH(B, C, D, A, X[12], 15);
        A = HH(A, B, C, D, X[2], 3);
        D = HH(D, A, B, C, X[10], 9);
        C = HH(C, D, A, B, X[6], 11);
        B = HH(B, C, D, A, X[14], 15);
        A = HH(A, B, C, D, X[1], 3);
        D = HH(D, A, B, C, X[9], 9);
        C = HH(C, D, A, B, X[5], 11);
        B = HH(B, C, D, A, X[13], 15);
        A = HH(A, B, C, D, X[3], 3);

La première chose à remarquer est que nous définissons une fonction async avec `yield`. C'est très similaire aux Dépendances avec `yield`.

{* ../../docs_src/events/tutorial003_py310.py hl[14:19] *}

La première partie de la fonction, avant le `yield`, sera exécutée **avant** le démarrage de l'application.

Et la partie après le `yield` sera exécutée **après** que l'application a terminé.

也許你要啟動新版本，或只是不想再跑它了。🤷

///

### Lifespan 函式 { #lifespan-function }

首先要注意的是，我們定義了一個帶有 `yield` 的 async 函式。這和帶有 `yield` 的依賴（Dependencies）非常相似。

{* ../../docs_src/events/tutorial003_py310.py hl[14:19] *}

函式在 `yield` 之前的部分，會在應用啟動前先執行。

`yield` 之後的部分，會在應用結束後再執行。

### 非同步內容管理器（Async Context Manager） { #async-context-manager }

你會看到這個函式被 `@asynccontextmanager` 裝飾。

Dikkat edilmesi gereken ilk şey, `yield` içeren async bir fonksiyon tanımlıyor olmamız. Bu, `yield` kullanan Dependencies’e oldukça benzer.

{* ../../docs_src/events/tutorial003_py310.py hl[14:19] *}

Fonksiyonun `yield`’den önceki kısmı, uygulama başlamadan **önce** çalışır.

`yield`’den sonraki kısım ise, uygulama işini bitirdikten **sonra** çalışır.

### Async Context Manager { #async-context-manager }

Lo primero que hay que notar es que estamos definiendo una función asíncrona con `yield`. Esto es muy similar a las Dependencias con `yield`.

{* ../../docs_src/events/tutorial003_py310.py hl[14:19] *}

La primera parte de la función, antes del `yield`, será ejecutada **antes** de que la aplicación comience.

Y la parte después del `yield` será ejecutada **después** de que la aplicación haya terminado.