anchor.diff:  [source,java]
   ----
   // executing.xml needs to have an execution protocol, e.g. CENTRAL_EXECUTOR
  -JChannel ch=new JChannel("/home/bela/executing.xml");
  -ExecutionService exec_service =new ExecutionService(ch);
  +JChannel ch = new JChannel("/home/bela/executing.xml");
  +ExecutionService exec_service = new ExecutionService(ch);
   ch.connect("exec-cluster");
   Future<Value> future = exec_service.submit(new MyCallable());
   try {
  
positive.code: 
  [source,java]
  ----
  ch=new JChannel(props);
  CounterService counter_service=new CounterService(ch);
  ch.connect("counter-cluster");
  Counter counter=counter_service.getOrCreateCounter("mycounter", 1);
  ----
  
  In the sample code above, we create a channel first, then create the `CounterService` referencing the channel.
  
negative.code: submitted via any ExecutionService in the cluster.
          
  Since an ExecutionService does not allow for non serializable class instances to be sent across as tasks
  there are two utility classes provided to get around this problem.  For users that are used to using a
  CompletionService with an Executor there is an equivalent ExecutionCompletionService provided that allows
  for a user to have the same functionality.  It would have been preferred to allow for the same
  ExecutorCompletionService to be used, but due to its implementation using a non serializable object
  