Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 48 for turnos (0.33 sec)

  1. docs/es/docs/async.md

    Podrías tener turnos como en el ejemplo de las hamburguesas, primero la sala de estar, luego la cocina, pero como no estás esperando 🕙 nada, solo limpiando y limpiando, los turnos no afectarían nada.
    
    Tomaría la misma cantidad de tiempo terminar con o sin turnos (concurrencia) y habrías hecho la misma cantidad de trabajo.
    
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Sun Aug 31 09:56:21 UTC 2025
    - 24.7K bytes
    - Viewed (0)
  2. docs/pt/docs/async.md

    Você poderia ter turnos como no exemplo dos hambúrgueres, primeiro a sala de estar, então a cozinha, mas como você não está esperando por nada, apenas limpando e limpando, as chamadas não afetariam em nada.
    
    Levaria o mesmo tempo para finalizar com ou sem turnos (concorrência) e você teria feito o mesmo tanto de trabalho.
    
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Sun Aug 31 09:56:21 UTC 2025
    - 23.6K bytes
    - Viewed (0)
  3. docs/pt/docs/deployment/docker.md

    E o sistema de contêiner com o **balanceador de carga** iria **distribuir as solicitações** para cada um dos contêineres com seu aplicativo **em turnos**. Portanto, cada solicitação poderia ser tratada por um dos múltiplos **contêineres replicados** executando seu aplicativo.
    
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Sat Nov 09 16:39:20 UTC 2024
    - 37.4K bytes
    - Viewed (0)
  4. docs/es/docs/deployment/docker.md

    Y el sistema de contenedores distribuido con el **load balancer** **distribuiría las requests** a cada uno de los contenedores **replicados** que ejecutan tu aplicación **en turnos**. Así, cada request podría ser manejado por uno de los múltiples **contenedores replicados** ejecutando tu aplicación.
    
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Fri May 30 13:15:52 UTC 2025
    - 31K bytes
    - Viewed (0)
  5. docs/en/docs/async.md

    There's no waiting 🕙 anywhere, just a lot of work to be done, on multiple places of the house.
    
    You could have turns as in the burgers example, first the living room, then the kitchen, but as you are not waiting 🕙 for anything, just cleaning and cleaning, the turns wouldn't affect anything.
    
    It would take the same amount of time to finish with or without turns (concurrency) and you would have done the same amount of work.
    
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Sun Aug 31 09:56:21 UTC 2025
    - 24K bytes
    - Viewed (0)
  6. internal/lru/lru.go

    const numBuckets = 100
    
    // NewLRU returns a new thread-safe cache with expirable entries.
    //
    // Size parameter set to 0 makes cache of unlimited size, e.g. turns LRU mechanism off.
    //
    // Providing 0 TTL turns expiring off.
    //
    // Delete expired entries every 1/100th of ttl value. Goroutine which deletes expired entries runs indefinitely.
    Registered: Sun Sep 07 09:35:13 UTC 2025
    - Last Modified: Fri Apr 25 08:22:26 UTC 2025
    - 12.5K bytes
    - Viewed (0)
  7. docs/tr/docs/async.md

    *Evet, tüm hikaye bu*.
    
    ---
    
    Beklemek yok 🕙. Hiçbir yerde.  Sadece evin birden fazla yerinde yapılacak fazlasıyla iş var.
    
    You could have turns as in the burgers example, first the living room, then the kitchen, but as you are not waiting 🕙 for anything, just cleaning and cleaning, the turns wouldn't affect anything.
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Sun Aug 31 09:56:21 UTC 2025
    - 21.8K bytes
    - Viewed (0)
  8. okhttp/src/commonJvmAndroid/kotlin/okhttp3/MultipartBody.kt

        /**
         * Appends a quoted-string to a StringBuilder.
         *
         * RFC 2388 is rather vague about how one should escape special characters in form-data
         * parameters, and as it turns out Firefox and Chrome actually do rather different things, and
         * both say in their comments that they're not really sure what the right approach is. We go
    Registered: Fri Sep 05 11:42:10 UTC 2025
    - Last Modified: Wed Mar 19 19:25:20 UTC 2025
    - 10.9K bytes
    - Viewed (0)
  9. docs/es/docs/help-fastapi.md

    * Noticias sobre FastAPI y amigos 🚀
    * Guías 📝
    * Funcionalidades ✨
    * Cambios importantes 🚨
    * Consejos y trucos ✅
    
    ## Sigue a FastAPI en X (Twitter)
    
    <a href="https://x.com/fastapi" class="external-link" target="_blank">Sigue a @fastapi en **X (Twitter)**</a> para obtener las últimas noticias sobre **FastAPI**. 🐦
    
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Sun Aug 31 10:49:48 UTC 2025
    - 14.5K bytes
    - Viewed (0)
  10. docs/bucket/replication/DESIGN.md

    delete replication should match to avoid inconsistent picture between the clusters. It is not recommended to turn on asymmetric replication - for e.g. if three sites A,B,C are participating in replication, it would be better to avoid replication setups like A -> [B, C], B -> A. In this particular example, an object uploaded to A will be replicated to B,C. If replica metadata sync is turned on in site B, any metadata updates on a replica version made in B would reflect in A, but not in C.
    
    ###...
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Tue Aug 12 18:20:36 UTC 2025
    - 14.7K bytes
    - Viewed (0)
Back to top