Remoting Architecture

From FirebugWiki

Revision as of 08:29, 15 August 2012 (edit) Honza (Talk | contribs) (→Proxy) ← Older edit		Revision as of 08:32, 15 August 2012 (edit) (undo) Honza (Talk | contribs) (→Proxy) Newer edit →
Line 15:		Line 15:
	[[Image:Panel-proxy-module.png]]		[[Image:Panel-proxy-module.png]]
		+
		+	* Panel (a view) should never use Module (a service) directly
		+	* The communication should always be done through the current proxy

---

Revision as of 08:32, 15 August 2012

This page is intended to summarize basic architecture concepts for Firebug (and Firebug extensions) remote capabilities (such as remote debugging or remote HTTP monitoring).

Resources

• HTTP Monitor
• Firebug 1.7 BTI
• Script Panel Refactoring

Proxy

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