_, err = loadSvcActRPC.Call(ctx, client.gridConn(), grid.NewMSSWith(map[string]string{
		peerRESTUser: accessKey,
	}))
	return err
}

// LoadGroup - send load group command to peers.
func (client *peerRESTClient) LoadGroup(ctx context.Context, group string) error {
	_, err := loadGroupRPC.Call(ctx, client.gridConn(), grid.NewMSSWith(map[string]string{
		peerRESTGroup: group,

## Recap { #recap }

You can now get the current user directly in your *path operation function*.

We are already halfway there.

We just need to add a *path operation* for the user/client to actually send the `username` and `password`.

         * response will not read a batched command and therefore
         * the 'received' member of the response object will not
         * be set to true indicating the send and sendTransaction
         * methods that the next part should be sent. This is a
         * very indirect and simple batching control mechanism.
         */

    }
    
    private void startAsyncNotification(ChangeNotificationHandle handle) {
        CompletableFuture.runAsync(() -> {
            while (handle.active) {
                try {
                    // Send SMB2 Change Notify request
                    Smb2ChangeNotifyRequest request = new Smb2ChangeNotifyRequest();
                    request.setFileId(handle.directoryFile.getFileId());

            while (attempt < MAX_REDIRECTS) {
                this.connection.setRequestProperty(this.authProperty, this.authMethod + ' ' + Base64.toBase64String(type1.toByteArray()));
                this.connection.connect(); // send type 1
                response = parseResponseCode();
                if (response != HTTP_UNAUTHORIZED && response != HTTP_PROXY_AUTH) {
                    return;
                }

    val requestHeadersEndListener =
      object : EventListener() {
        override fun requestHeadersEnd(
          call: Call,
          request: Request,
        ) {
          // Wait for the server to send the duplex response before acting on the 301 response
          // and resetting the stream.
          duplexResponseSent.await()
        }
      }
    client =
      client
        .newBuilder()

	return s.newCache, nil
}

// sendUpdate() should be called on a regular basis when the newCache contains more recent total than previously.
// May or may not send an update upstream.
func (f *folderScanner) sendUpdate() {
	// Send at most an update every minute.
	if f.updates == nil || time.Since(f.lastUpdate) < time.Minute {
		return
	}
	if flat := f.updateCache.sizeRecursive(f.newCache.Info.Name); flat != nil {

  val headers: List<String>? by option("-H", "--header").help("Custom header to pass to server").multiple()

  val userAgent: String by option(
    "-A",
    "--user-agent",
  ).help(
    "User-Agent to send to server",
  ).default(NAME + "/" + versionString())

  val connectTimeout: Int by option(
    "--connect-timeout",
  ).help(
    "Maximum time allowed for connection (seconds)",
  ).int()

MinIO batch jobs framework also provides

- Retrying a failed job automatically driven by user input
- Monitoring job progress in real-time
- Send notifications upon completion or failure to user configured target

Following YAML describes the structure of a replication job, each value is documented and self-describing.

```yaml
replicate:
  apiVersion: v1

            updateProperty(Constants.NOTIFICATION_TO_PROPERTY, form.notificationTo);
            systemProperties.store();
        } catch (final Exception e) {
            logger.warn("Failed to send a test mail.", e);
            saveError(messages -> messages.addErrorsFailedToSendTestmail(GLOBAL));
        }

        return redirectByParam(AdminGeneralAction.class, "notificationTo", form.notificationTo);
    }