code wiki / _hdl_build / nx_video_native_client_gate.nx
nx_video_native_client_gate.nx
buildroot/runtime/_hdl_build/nx_video_native_client_gate.nx
about
nx_video_native_client_gate.nx -- MOBILE-FIRST, ZERO-JS proof (task #22). A pure-NishiLang client with
NO browser, NO JavaScript, and NO wasm is a FULL room participant on the LIVE edge: native peer A packs a
REAL room chat message with the SAME core the browser runs (vc_chat_pack -> vc_wire_pack, kind 0x43),
sends it over sovereign TLS-1.3 + RFC-6455 WSS to nishifamily.com/signal/<room>, and native peer B
RECEIVES it via the relay's content-blind broadcast and parses it back with the SAME core (vc_wire_parse
-> vc_chat_parse), asserting kind 0x43 and byte-exact text. GREEN = the mobile-native core works end to
end on the real relay. This is the concrete answer to "why JS": for anything that isn't a stock browser,
we use NONE -- the identical NishiLang core runs native (and compiles to ARM for a phone the same way).
usage: nx_video_native_client_gate (room fixed "nxnative")
expect_exit: 0 license_tier: ORIGINAL
dependencies 2 imports · 0 importers
imports: nx_ws_client_session.nxnx_video_client_wasm.nx
imported by: nobody (leaf or entry point)
call flow from main pre-order; caps 40 nodes / depth 6 declared; ↻ = already shown
structs
| none |
consts
| none |
functions
| 14 | func nw(s: *u8) -> i64 { var n: i64=0; while s[n]!=(0 as u8){n=n+1} sys_write(1,s,n); return 0 } called by 1: main |
| 15 | func nn(v: i64) -> i64 |
| 19 | func fwln(fd: i64, s: *u8) -> i64 { var n: i64=0; while s[n]!=(0 as u8){n=n+1} sys_write(fd,s,n); return 0 } |
| 21 | func main() -> i64 |