Resources

Download

Working HTTP Monitor (Firefox extension) is available.
See also the instructions about how to use it.
The goal of the HTTP Monitor component is to be shared between Firebug (an extension) and Firefox (built-in tool).

Architecture

Core architecture is based on the Net Panel and adapted to also support remote HTTP tracking.

Local Network Event Flow

This sequence diagram describes local monitoring scenario where the user tracks a browser tab on local browser.

HTTP Observer Observes HTTP traffic of the selected tab and sends every event to NetProgress object.

NetProgress object processes incoming HTTP event and produces a File object that represents the HTTP request. It uses an existing File object if there is already one created for the request. The File is further passed to Net Panel

NetPanel stores the file in a queue. Files in the queue are processed and rendered asynchronously on a timeout.

Remote Network Event Flow

This sequence diagram describes remote monitoring scenario where the user tracks a browser tab on remote browser. The flow shows how HTTP events are transported from the server to the client.

HTTP Observer running on the server side send every HTTP event to the NetProgress instance (also on the server side)

NetProgress object processes incoming HTTP event and produces a File object (or uses an existing one) that represents the HTTP request. The File is further passed to NetworkMonitorActor

NetworkMonitorActor stores the file in a queue that is processed asynchronously on a timeout and send in chunks (more files at once) over TCP/IP to the client.

Connection object on the client side receives a packet and passes it to a Protocol object.

Protocol object understands structure of the packet and passes it further to a RemoteProxy object.

RemoteProxy gets all files in the packet and passes it further to the NetPanel object.

NetPanel stores the file in a queue. Files in the queue are processed and rendered asynchronously on a timeout.