Simple example contrasting a client with baked-in timeout functionality and a client composed with a timeout filter.

finagle-client-timeout-example.scala

import com.twitter.conversions.time._
import com.twitter.finagle.client._
import com.twitter.finagle.dispatch.SerialClientDispatcher
import com.twitter.finagle.util.DefaultTimer
import com.twitter.util.{Await, Future}

trait ExampleClient {
  def client: Service[String, String]

  def sa = new java.net.InetSocketAddress("localhost", 8080)
  def sr = com.twitter.finagle.stats.NullStatsReceiver

  def bridge: Future[Service[String, String]] =
    StringClientTransporter(sa, sr) map { transport =>
      new SerialClientDispatcher(transport)
    }

  def run() {
    val result = client("hello")
    println(Await.result(result))
  }
}

object KludgyClient extends ExampleClient {
  implicit val timer = DefaultTimer.twitter

  val client = new Service[String, String] {
    def apply(req: String) = bridge flatMap { svc =>
      svc(req) ensure svc.close()
    } within 500.milliseconds
  }
}

object ClientWithTimeoutFilter extends ExampleClient {
  import com.twitter.finagle.service.TimeoutFilter

  val timeout = new TimeoutFilter[String, String](
    timeout = 500.milliseconds,
    timer = DefaultTimer.twitter
  )

  val client = timeout andThen new Service[String, String] {
    def apply(req: String) = bridge flatMap { svc =>
      svc(req) ensure svc.close()
    }
  }
}