title: ActorSelection versus ActorRef - migrating from actorFor to actorSelection
body: <p>Akka has deprecated <code>actorFor</code> in favor of <code>actorSelection</code>.  The former returns an <code>ActorRef</code> while the latter returns an <code>ActorSelection</code> which could be a collection of <code>ActorRef</code>s.</p>
  
  <p>When migrating from <code>actorFor</code> to <code>actorSelection</code>, you have a couple of optoins:</p>
  
  <p>Option 1: Both <code>ActorSelection</code> and <code>ActorRef</code> have a <code>tell</code> method, so you could almost exchange <code>actorSelection</code> for <code>actorFor</code> (this is not always true - <code>ask</code> is not the same and <code>actorSelection</code> could point to multiple <code>ActorRef</code>s) so long as there is only one actor for that selection and you are only <code>tell</code>ing the actor.</p>
  
  <p>Option 2: Get an <code>ActorRef</code> from the <code>ActorSelection</code>.  This can be done using either <code>Identify</code> (which involves a couple more messages) or <code>resolveOne</code> (which involves a <code>Future</code>).</p>
  
  <p>In Option 1, what kind of overhead does <code>ActorSelection</code> add compared to the <code>ActorRef</code> from <code>actorFor</code>?</p>
  
  <p>Is there a better option than the ones listed above?</p>