Attention is currently required from: Hoernchen, fixeria, laforge, osmith, pespin.

View Change

1 comment:

• Patchset:

  • Patch Set #1:

    I'm not really following here. […]

    For Web applications, we need tighter integration between osmo-bts-trx and osmo-trx for the following reasons:
    1. To enable fast in-process interaction instead of communicating over UDP
    2. To build and deliver a single combined library (e.g. osmo-bts.wasm) for use in the browser
    3. To improve performance by eliminating socket-based IPC overhead and context switching

    In this architecture, both components are compiled into one unified WebAssembly target, so linking the relevant parts together at build time is intentional. This allows direct function calls instead of network transport and avoids serialization/deserialization overhead.

    Further in the web deployment model, osmo-bts (running inside WebAssembly in the browser) communicates with the backend over WebSocket. On the backend side, a gateway component converts messages to/from UDP in order to interoperate with the remaining native Osmocom components.

    A more detailed architectural description can be found here: https://github.com/wavelet-lab/osmoweb/blob/main/docs/architecture/overview.md

To view, visit change 42243. To unsubscribe, or for help writing mail filters, visit settings.