Crossfire 0.2 Planning
From FirebugWiki
This page exists to discuss planned changes and additions for the 0.2 release of the Crossfire extension and protocol. While the first release was largely based on other existing work, we now have feedback from actual usage that we should apply to a next version.
Proposed changes:
Contents |
[edit] Breakpoints
- Breakpoint handles should be unique across contexts, not just per context.
- Breakpoint JSON contains some unused properties, others may need to be added to support Firebug 1.5 HTML Breakpoints, etc.
- the
changebreakpointcommand can be ignored in favor of add/remove. Should we remove it? The verdict was NO.
[edit] Contexts
- Adding an additional command like e.g.
get_context { "context_id" }that would return the FirebugContext object for that context, to support remote/mobile/multi-process?
[edit] Transports
- Test socket transport in both directions (listen/connect).
- Add XHR transport?
- WebSockets?
[edit] Synchronous Option
Currently all the commands/requests in Crossfire happen asynchronously. But, in some cases (e.g. onContextCreated or onScript) it could be useful to use synchronous I/O, which would allow additional commands to be processed before execution continues. Use case: set breakpoints in a script immediately following an onScript event, so that top-level breakpoints will be hit the first time the script is executed.
[edit] Modules
- Port Crossfire Packet module to use CommonJS style loader?
