*/
    protected String escapeValue(final String action) {
        return action.replace('\t', ' ');
    }

    /**
     * Outputs a log message using the statistics logger.
     *
     * @param buf the string buffer containing the log message
     */
    protected void log(final StringBuilder buf) {
        statsLogger.info(buf.toString());
    }

    /**

    }

    /**
     * Checks if the given filename is a log file based on its extension.
     *
     * @param name the filename to check
     * @return true if the file is a log file (.log or .log.gz), false otherwise
     */
    protected boolean isLogFilename(final String name) {
        return name.endsWith(".log") || name.endsWith(".log.gz");
    }

    /**

      if (state != null) {
        // Log before the transition, so that if the process exits in response to server failure,
        // there is a higher likelihood that the cause will be in the logs.
        boolean log = !(service instanceof NoOpService);
        /*
         * We have already exposed startup exceptions to the user in the form of suppressed
         * exceptions. We don't need to log those exceptions again.
         */

    /** Property key for log notification enabled configuration. */
    public static final String LOG_NOTIFICATION_ENABLED_PROPERTY = "log.notification.enabled";

    /** Property key for log notification level configuration. */
    public static final String LOG_NOTIFICATION_LEVEL_PROPERTY = "fess.log.notification.level";

            "The account used is a Computer Account. Use your global user account or local user account to access this server.",
            "The user must change his password before he logs on the first time.", "The object was not found.",
            "The referenced account is currently locked out and may not be logged on to.", "Connection refused",
            "The remote system is not reachable by the transport.",

       * TODO(cpovirk): Do we really want to log this if we called setException(throwable) and it
       * returned true? This was intentional (CL 46470009), but it seems odd compared to how we
       * normally handle Error.
       *
       * Similarly, do we really want to log the same Error more than once?
       */
      log(throwable);
    }
  }

  private static void log(Throwable throwable) {
    String message =

Se ve así:

```
data: {"name": "Portal Gun", "price": 999.99}

data: {"name": "Plumbus", "price": 32.99}

```

SSE se usa comúnmente para streaming de chat de IA, notificaciones en vivo, logs y observabilidad, y otros casos donde el servidor envía actualizaciones al cliente.

/// tip | Consejo

It looks like this:

```
data: {"name": "Portal Gun", "price": 999.99}

data: {"name": "Plumbus", "price": 32.99}

```

SSE is commonly used for AI chat streaming, live notifications, logs and observability, and other cases where the server pushes updates to the client.

/// tip

If you want to stream binary data, for example video or audio, check the advanced guide: [Stream Data](../advanced/stream-data.md).

 * offering expected O(n + k log k) performance (worst case O(n log k)) for n calls to {@link
 * #offer} and a call to {@link #topK}, with O(k) memory. In comparison, quickselect has the same
 * asymptotics but requires O(n) memory, and a {@code PriorityQueue} implementation takes O(n log
 * k). In benchmarks, this implementation performs at least as well as either implementation, and

        }
    }

    /**
     * Logs a message to the annotation processing environment.
     *
     * @param kind the kind of diagnostic message
     * @param message the message to log
     */
    private void logMessage(Diagnostic.Kind kind, String message) {
        processingEnv.getMessager().printMessage(kind, message);
    }

    /**