anchor.diff:  %%
   %% %CopyrightBegin%
   %%
  -%% Copyright Ericsson AB 2010-2011. All Rights Reserved.
  +%% Copyright Ericsson AB 2010-2012. All Rights Reserved.
   %%
   %% The contents of this file are subject to the Erlang Public License,
   %% Version 1.1, (the "License"); you may not use this file except in
  
positive.code: 
  fetch(Tid, Key) ->
      [T] = ets:lookup(Tid, Key),
      T.
  
  %%% ---------------------------------------------------------------------------
  %%% # connection_up/3
  
negative.code:     reconnect(Pid, S),
      ok;
  
  %% Watchdog is sending notification of a state transition. Note that
  %% the connection_up/down messages are pre-date this message and are
  %% still used. A 'watchdog' message will follow these and communicate
  %% the same state as was set in handling connection_up/down.
  transition({watchdog, Pid, {TPid, From, To}}, #state{service_name = SvcName,
                                                       peerT = PeerT}) ->
      #peer{ref = Ref, type = T, options = Opts, op_state = {OS,_}}
          = P
          = fetch(PeerT, Pid),
      insert(PeerT, P#peer{op_state = {OS, To}}),
      send_event(SvcName, {watchdog, Ref, TPid, {From, To}, {T, Opts}}),
      ok;
  %% Death of a peer process results in the removal of it's peer and any
  %% associated conn record when 'DOWN' is received (after this) but the
  %% states will be {?STATE_UP, ?WD_DOWN} for a short time. (No real
  %% problem since ?WD_* is only used in service_info.) We set ?WD_OKAY
  %% as a consequence of connection_up since we know a watchdog is
  %% coming. We can't set anything at connection_down since we don't
  %% know if the subsequent watchdog message will be ?WD_DOWN or
  %% ?WD_SUSPECT. We don't (yet) set ?STATE_* as a consequence of a
  %% watchdog message since this requires changing some of the matching
  %% on ?STATE_*.
  %%
  %% Death of a conn process results in connection_down followed by
  %% watchdog ?WD_DOWN. The latter doesn't result in the conn record
  %% being deleted since 'DOWN' from death of its peer doesn't (yet)
  %% deal with the record having been removed.
  
  %% Monitor process has died. Just die with a reason that tells
  %% diameter_config about the happening. If a cleaner shutdown is
  