Hi all,
I’m Yash (VictoWolf) ,
I was going through DevTools Network panel architecture while preparing to contribute on the idea:
“Add WebSocket/gRPC support to the Network panel.”
I wanted to understand how HTTP entries are currently produced.
From reading the code and docs, what i think is:
- The Network tab does not inspect network traffic directly
- It relies on timeline events exposed via the VM service
HttpClient emits structured lifecycle events that DevTools converts into NetworkRequest objects
So for non-HTTP protocols,
My idea was to run a few apps using:
- WebSocket.connect
- raw Socket
- a gRPC client
Then inspect the timeline stream and see:
- what events actually exist
- whether a websocket/grpc session can already be reconstructed
- or if there’s simply not enough signal
Based on findings, design a connection-oriented model rather than a request-oriented one.
Before I go down the wrong path:
I wanted to know, do WebSocket and gRPC communications already emit sufficient timeline information intended for tooling to interpret, or is part of this project expected to involve introducing new VM/service instrumentation?
@elliette @srawlins — I’d appreciate guidance on whether I’m investigating the correct layer.
Thanks!