anchor.diff:  guardian_process(FunctionPid, AccumulatorPid, PoolPid, DyingMessage) ->
       erlang:monitor(process, FunctionPid),
       erlang:monitor(process, AccumulatorPid),
  -    erlang:monitor(process, PoolPid),	
  +    erlang:monitor(process, PoolPid),   
       receive
           {'DOWN', _, process, FunctionPid, _} ->
               % The AsyncFunction process has died. 
  
positive.code:     TimerRef = rpc:call(AccumulatorNode, erlang, send_after, [Timeout, AccumulatorPid, {add_actions, []}]),
      AccumulatorPid!{get_actions_blocking, self()},
      receive 
          {actions, X} -> erlang:cancel_timer(TimerRef), X;			
          Other -> ?PRINT({unhandled_event, Other}), []
      end.
  
  
negative.code: 
      % Create a process for the AsyncFunction...
      FunctionPid = case Record#comet.function of
          F when is_function(F) -> spawn_with_context(F,postback);
          P when is_pid(P) -> 
              %% If P is a pid, then it was initiated on the page
              %% and that means we have to kill the checker pid that's
              %% waiting to kill it for us.  Hacky, I know. Real
              %% spaghetti-like. I don't particularly like it, but it
              %% fixes the bug.
              {ok,CheckerPid} = get_accumulator_checker_pid(P),
              CheckerPid ! accumulator_started,
              P
      end,
  
      % Create a process for the AsyncGuardian...
  