Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for Lively (0.44 sec)

  1. internal/grid/README.md

    Do *not* use the MinIO Grid for:
    
    * Large payloads.
    
    Only a single connection is ever made between two servers.
    Likely this means that this connection will not be able to saturate network bandwidth.
    Therefore, using this for large payloads will likely be slower than using a separate connection,
    and other connections will be blocked while the large payload is being sent.
    
    ## Handlers & Routes
    
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Thu Jan 18 07:03:17 GMT 2024
    - 9.4K bytes
    - Viewed (0)
  2. CREDITS

      If it is not possible or desirable to put the notice in a particular
      file, then You may include the notice in a location (such as a LICENSE
      file in a relevant directory) where a recipient would be likely to
      look for such a notice.
    
      You may add additional accurate notices of copyright ownership.
    
    ================================================================
    
    github.com/elastic/go-elasticsearch/v7
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Fri Apr 26 06:31:35 GMT 2024
    - 1.6M bytes
    - Viewed (0)
  3. docs/bucket/replication/README.md

    #### Rationale
    
    - SSE-C requires application to remember the keys for all GET/PUT operations, any unfortunate loss of keys would automatically mean the objects cannot be accessed anymore.
    - SSE-C is hardly adopted by most widely used applications, applications prefer server to manage the keys via SSE-KMS or SSE-S3.
    - MinIO recommends applications to use SSE-KMS, SSE-S3 for simpler, safer and robust encryption mechanism for replicated buckets.
    
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Tue Jan 24 23:46:33 GMT 2023
    - 18.2K bytes
    - Viewed (0)
Back to top