}

    @Override
    protected long getBufferAddress(ByteBuffer buffer) {
        // Return a fake address for TCP
        // In real RDMA implementations, this would be the native memory address
        return buffer.hashCode();
    }

import org.junit.jupiter.params.provider.ArgumentsSource
import org.junit.jupiter.params.support.ParameterDeclarations

/**
 * This enforces us having the params classes on the classpath to workaround
 * https://github.com/graalvm/native-build-tools/issues/745
 */
class WithArgumentSourceTest {
  @ParameterizedTest
  @ArgumentsSource(FakeArgumentsProvider::class)
  fun passingTest(value: Int) {
    assertThat(value).isGreaterThan(0)
  }
}

  %MAVEN_OPTS% ^
  %JVM_CONFIG_MAVEN_OPTS% ^
  %MAVEN_DEBUG_OPTS% ^
  --enable-native-access=ALL-UNNAMED ^
  -classpath %LAUNCHER_JAR% ^
  "-Dclassworlds.conf=%CLASSWORLDS_CONF%" ^
  "-Dmaven.home=%MAVEN_HOME%" ^
  "-Dmaven.mainClass=%MAVEN_MAIN_CLASS%" ^
  "-Dlibrary.jline.path=%MAVEN_HOME%\lib\jline-native" ^
  "-Dmaven.multiModuleProjectDirectory=%MAVEN_PROJECTBASEDIR%" ^
  %LAUNCHER_CLASS% ^
  %MAVEN_ARGS% ^

    return result;
  }

  /*
   * If I understand correctly:
   *
   * This needs to be a @JsMethod so that J2CL knows to look for a JavaScript implemention of
   * it in Platform.native.js. (The JavaScript implementation inline below is visible to *GWT*, but
   * *J2CL* doesn't look at it.)
   *
   * However, once it's a @JsMethod, GWT produces a warning. That's because (a) the *other* purpose

  // 7.1.0 is used because it avoids this error
  // Could not create an instance of type aQute.bnd.gradle.BundleTaskExtension.
  // Cannot change attributes of configuration ':native-image-tests:compileClasspath' after it has been locked for mutation
  implementation("biz.aQute.bnd:biz.aQute.bnd.gradle:7.1.0")

Queremos obtener el `current_user` *solo* si este usuario está activo.

Entonces, creamos una dependencia adicional `get_current_active_user` que a su vez utiliza `get_current_user` como dependencia.

Ambas dependencias solo devolverán un error HTTP si el usuario no existe, o si está inactivo.

Así que, en nuestro endpoint, solo obtendremos un usuario si el usuario existe, fue autenticado correctamente, y está activo:

  "durations" : [ {
    "testProject" : "bigCppApp",
    "linux" : 137
  }, {
    "testProject" : "bigCppMulti",
    "linux" : 257
  } ]
}, {
  "scenario" : "org.gradle.performance.regression.nativeplatform.NativeCleanBuildPerformanceTest.clean assemble (native, parallel)",
  "durations" : [ {
    "testProject" : "manyProjectsNative",

  }

  val javaVersionSetting =
    if (testJavaVersion > 8 && (project.name == "okcurl" || project.name == "native-image-tests")) {
      // Depends on native-image-tools which is 17+, but avoids on Java 8 tests
      "17"
    } else {
      "1.8"
    }

  val projectJvmTarget = JvmTarget.fromTarget(javaVersionSetting)

val androidBuild: String by settings
val graalBuild: String by settings
val loomBuild: String by settings

if (androidBuild.toBoolean()) {
  include(":regression-test")
}

if (graalBuild.toBoolean()) {
  include(":native-image-tests")
}

include(":okcurl")
include(":okhttp")
include(":okhttp-bom")
include(":okhttp-brotli")
include(":okhttp-coroutines")
include(":okhttp-dnsoverhttps")
include(":okhttp-hpacktests")

And to communicate using WebSockets with your backend you would probably use your frontend's utilities.

Or you might have a native mobile application that communicates with your WebSocket backend directly, in native code.

Or you might have any other way to communicate with the WebSocket endpoint.

---