Q51: What is the RSC Wire Format (Flight Protocol) and how does the client reconcile it into the DOM?
The RSC Wire Format is a streaming, line-delimited JSON-like serialization protocol emitted by the server. Instead of sending raw HTML or client JS bundles, it streams typed tuples representing Virtual DOM nodes, component props, suspended promises, and client module references ($L1, $S2). The client runtime reads this stream incrementally and reconciles VDOM nodes directly without resetting client state.
RSC Flight Stream Parsing & Reconciliation Pipeline
Conceptual Flight Stream Response Line
M1:{"id":"./src/Header.client.js","chunks":["main"],"name":"default"}
J0:["$","div",null,{"children":["$","$L1",null,{"title":"Live Feed"}]}]
P2:{"status":"fulfilled","value":{"id":101}}💡 M lines register client module chunks; J lines construct VDOM node trees referencing client modules ($L1) and promises ($P2).
Key Takeaways
- Encodes Virtual DOM structures, client module boundaries, and pending Suspense promises into a single line-delimited stream.
- Allows soft client-side route transitions to patch VDOM trees while preserving state in active Client Components.
Knowledge Check
What primary operational benefit does the RSC Wire Format offer during client-side route transitions?