Client Communication

The browser or Electron shell receives rendered markup plus a callback bridge. When the user interacts with an element, the shell sends the event identity back to the server. The server looks up the callback under the active user and page, invokes it with the recorded this-binding, and can rerender the component tree.

This pattern makes the client very thin, but it also makes latency and connection management part of the rendering model. It works best for experiments, internal tools, or controlled desktop shells where server-owned state is a feature rather than an accident.

• ServerManager supplies the process port and communication settings.
• CallbackManager stores callbacks by user, page, and callback ID.
• ScreenSizeManager lets server components query user-specific viewport information.
• The Juice Messenger application surface demonstrates state changes and callback-triggered rerendering.