This page is intended to summarize basic architecture concepts for Firebug (and Firebug extensions) remote capabilities (such as remote debugging or remote HTTP monitoring).
The proxy object represents a connection between a panel (front end) and a module (back end).
The proxy has essentially two implementations:
- Local - direct API calls
- Remote - communication over TCP/IP protocol
- Panel (a view) should never use Module (a service) directly
- The communication should always be done through the current proxy
- Each Panel should have its own proxy that implements API of the remote module (service)
- There can be also proxy objects used by non-panel objects, e.g. the Profiler
- It should be possible to create new proxies in extensions.
- There should be also something like a default (or global) proxy that can be used for things like getting list of tabs on the remote browser
Here is a more detailed diagram with local and remote proxies.
- Panel object at the top is referencing its proxy object
- The proxy implementation can be local or remote
- Local proxy uses direct API calls (in process) and asynchronous callbacks
- Remote proxy uses TCP/IP connection to communicate with the back-end using JSON packets
- The remote communication is based on RDP
- The server side implements Actor, which is responsible for communication with specific proxy
- The actor is finally consuming back-end Module (service) API
Connection object is responsible for sending properly setup packets to the server and handling all response packets. This object is also responsible for handling any errors (or error packets) that can occur during the communication.
- Remote proxies should always use the connection object to send JSON packets
- The connection is singleton it'll be probably attached to the global Firebug object
Firebug also needs its server side implementation that will be used if Firebug is running in a server mode (on the remote browser). In such cases only back-end services like: NetMonitor or Debugger modules will be loaded and activated. UI overlays (i.e. browserOverlay.js) shouldn't be loaded at all since it isn't necessary and e.g. Fennec UI doesn't even have expected XUL elements to be overlayed.
Individual services should be always loaded on-demand at the time when appropriate actor is requested by the client side. For example, when the client side requests a net actor then NetMonitor module should be loaded and activated.
- Only actors are registered on the server side by default
- Actors are responsible for loading and activating back-end services
- Do we want to also delay AMD module load?
- Extensions should be able to create and register custom actors
This section describes the current BTI (Browser Tools Interface) concepts. These concepts should be reviewed and refactored as necessary.
WebApp represents a browsing context. Browsing context is an environment in which Document objects are presented to the user. Instance of this object is associated with top level page window (it's on the same level as the context object).
This object doesn't implement any logic it's there only to demonstrate the concept.
- list of breakpoints
- reference to the current context