michbarsinai / bp-javascript-search Goto Github PK

Because we should etc.

Use an adapter object, like in the LSCoBPJS package.

So we can put the whole Eclipse/NetBeans thing behind us.
Also, add code coverage while we're at it.

Need to update the documentation to reflect the fact we're doing a general BP library.

Arbiter should be a strategy, really. Event logging should be done in BP.

Currently seem to silently fail?

Process for swapping BThreads:

1. When the original BThreads were loaded, they registered a handler for breakUpon:

this.onBreakUpon = function( evt, externalEventQueue ) {
    if ( evt.type === "REMOVE_XXX" ) {
        var state = { ... get the state ... }
        externalEventQueue.push( pjs.Event("REMOVED_XXX", state) );
        }
}

1. New BThreads are loaded. Each one requests the REMOVE events for all the BThreads it replaces. It then waits for the REMOVED event, and reads the state.
2. New BThreads register their own breakUpon handlers.

Advantages:

• BThreads get a chance to clean up and arrange status transfer before they go.
• In line with BP idioms
• On critical times, it's easy to prevent software updates - just block all "REMOVE" events.

Problems:

• At the moment, we need to mention that we breakUpon these events on every BSync.

Currently they're deprecated + warning message.

as in:

bsync( {request: e1, waitFor:[e2,e3]} );

So calls to bsync may become:

bsync({request:bp.Event("abc")}, "hot");
bsync({request:bp.Event("abc")}, {temp:"hot", foo:"bar"});

So we can actually verify programs.

as there must be a close() call for every enter() call, and this design does not enforce that. Might want to use Try-With0Resources, or maybe create a function "withGlobalContext" that gets a (context)=>Void function block.

Handler should collect variables and the current line number of the removed BThread, and then publish them in an event.

Continuation of #9.