Skip to content

Crossfire 0.3a5 to 0.3a6 migration

Mike Rennie edited this page Aug 9, 2012 · 6 revisions

Crossfire 0.3a6 Migration

During 0.3a6 development there was a lot of work done to make the protocol more consistent and coherent, as expected, this work brought with it many changes to the protocol and a few changes that are no longer compatible with existing versions of Crossfire. This guide will help ease the transition from using a pre-0.3a6 version of Crossfire, with each affected protocol entity described in its own following section.

Contents

changebreakpoint

The changebreakpoint request has been updated to allow the context_id argument to be optional.

If omitted, Crossfire will attempt to change all known breakpoints in all known contexts that match the given request location.

Action Required

None, clients can optionally send or not send the context_id.

Details

No additional details

clearbreakpoint

The clearbreakpoint request has been updated to allow the context_id argument to be optional.

If omitted, Crossfire will attempt to clear the breakpoint from all known contexts

Action Required

None, clients can optionally send or not send the context_id.

Details

No additional details

getbreakpoints

The getbreakpoints request has been updated to allow the context_id argument to be optional.

If omitted, Crossfire will attempt to find all breakpoints in all contexts known to Firebug

Action Required

None, clients can optionally send or not send the context_id.

Details

No additional details

setbreakpoint

The setbreakpoint request has been updated to allow the context_id argument to be optional.

If omitted, Crossfire will attempt to set the breakpoint in all scripts that match the request locale.

Action Required

None, clients can optionally send or not send the context_id.

Details

No additional details