healthcheck:
    test: ["CMD", "mc", "ready", "local"]
    interval: 5s
    timeout: 5s
    retries: 5

# starts 4 docker containers running minio server instances.
# using nginx reverse proxy, load balancing, you can access
# it through port 9000.
services:
  minio1:
    <<: *minio-common
    hostname: minio1
    volumes:
      - edata1-1:/edata1

   * immediately reflected in the other. However, multiset changes may or may not be reflected in
   * any {@code Entry} instances already retrieved from the entry set (this is
   * implementation-dependent). Furthermore, implementations are not required to support
   * modifications to the entry set at all, and the {@code Entry} instances themselves don't even
   * have methods for modification. See the specific implementation class for more details on how

But we want to be able to parameterize that fixed content.

## A "callable" instance { #a-callable-instance }

In Python there's a way to make an instance of a class a "callable".

Not the class itself (which is already a callable), but an instance of that class.

To do that, we declare a method `__call__`:

{* ../../docs_src/dependencies/tutorial011_an_py310.py hl[12] *}

    instance := grid.NewStream[*Payload, *Req, *Resp](h, newPayload, newReq, newResp)

    // Tweakable options
    instance.WithPayload = true // default true when newPayload != nil
    instance.OutCapacity = 1    // default
    instance.InCapacity = 1     // default true when newReq != nil

    // Register the handler on the manager
    instance.Register(manager, handler, "asubroute")

        // Verify that the configuration was queried for notify buffer size
        verify(mockConfig, atLeastOnce()).getNotifyBufferSize();
    }

    @Test
    @DisplayName("Test multiple instances independence")
    void testMultipleInstancesIndependence() {
        NtTransNotifyChange notify1 = new NtTransNotifyChange(mockConfig, 0x1111, FILE_NOTIFY_CHANGE_FILE_NAME, false);

## Crear una instance { #create-an-instance }

Podríamos crear una instance de esta clase con:

{* ../../docs_src/dependencies/tutorial011_an_py310.py hl[18] *}

Y de esa manera podemos "parametrizar" nuestra dependencia, que ahora tiene `"bar"` dentro de ella, como el atributo `checker.fixed_content`.

## Usar la instance como una dependencia { #use-the-instance-as-a-dependency }

        return factory;
    }

    /**
     * Creates a new instance of {@link SAXParser} using the default configuration of {@link SAXParserFactory}.
     *
     * @return A new instance of {@link SAXParser}.
     */
    public static SAXParser newSAXParser() {
        return newSAXParser(newInstance());
    }

    /**
     * Creates a new instance of {@link SAXParser} using the specified {@link SAXParserFactory}.
     *

	</component>

	<component name="fessFileTransformer" class="org.codelibs.fess.crawler.transformer.FessFileTransformer" instance="singleton">
		<property name="name">"fessFileTransformer"</property>
	</component>

	<component name="fessStandardTransformer" class="org.codelibs.fess.crawler.transformer.FessStandardTransformer" instance="singleton">
		<property name="name">"fessStandardTransformer"</property>
	</component>

 The following are generated from this model:

   * {{{./apidocs/index.html}Java sources}} with <<<Builder>>> inner classes for immutable instances creation.

 See also corresponding {{{../../compat/maven-toolchain-model/index.html}Maven classical toolchains model documentation}}.

    T getSinkContents() throws IOException;
  }

  /** Factory for {@link ByteSource} instances. */
  interface ByteSourceFactory extends SourceFactory<ByteSource, byte[]> {}

  /** Factory for {@link ByteSink} instances. */
  interface ByteSinkFactory extends SinkFactory<ByteSink, byte[]> {}

  /** Factory for {@link CharSource} instances. */
  interface CharSourceFactory extends SourceFactory<CharSource, String> {}