vgi-rpc 0.2.0

//! The `__transport_options__` RPC method — transport capability negotiation.
//!
//! A framework-level handshake, parallel to `__describe__` (see
//! [`crate::introspect`]). The client calls it once per worker, before `init`,
//! to discover which transport features the worker supports; the shared-memory
//! side-channel (and, later, compression / AEAD) is used only when both peers
//! advertise support.
//!
//! Capabilities ride as request/response *metadata* under the
//! `vgi_rpc.transport.*` namespace (not as batch rows), consistent with how the
//! SHM segment itself is advertised and decode-safe (the params batch stays
//! empty). Each capability is one `vgi_rpc.transport.<name>` key with a string
//! value; unknown keys are ignored, so the set is open-ended.
//!
//! Mirrors Python `vgi_rpc.transport_options` byte-for-byte on the wire.

use crate::metadata::TRANSPORT_SHM_KEY;
use crate::wire::Metadata;

/// The reserved method name for the transport-capability handshake.
pub const TRANSPORT_OPTIONS_METHOD_NAME: &str = "__transport_options__";

/// Whether this worker can use the POSIX shared-memory side-channel.
///
/// The VGI shm channel is POSIX named shared memory (`shm_open`/`mmap`), which
/// interoperates across the C++/Java/Go/Python peers on Linux and macOS. It is
/// only compiled in under the `shm` feature, and Windows' shared-memory backing
/// is non-interoperable, so shm is offered only on POSIX builds with the
/// feature enabled.
pub fn shm_available() -> bool {
    cfg!(feature = "shm") && !cfg!(windows)
}

/// This worker's transport capabilities, as `__transport_options__` response
/// metadata. String values mirror Python's `b"true"` / `b"false"` byte values
/// once serialized onto the wire.
pub fn worker_transport_metadata() -> Metadata {
    let mut md = Metadata::new();
    md.insert(
        TRANSPORT_SHM_KEY.to_string(),
        if shm_available() { "true" } else { "false" }.to_string(),
    );
    md
}