Provide a simple builtin websocket client in `cask.WsClient`

Harmonize the actor-based APIs of `cask.WsClient`/`cask.WsHandler`/`cask.WsActor`, letting them share the same set of `cask.Ws` events

The default implementation of `cask.WsClient` on the JVM spawns one thread per connection, and doesn't really scale to large numbers of connections. For now we just continue using AsyncHttpClient in the load tests. Wrapping AsyncHttpClient in a nice API is TBD

1 files changed, 16 insertions, 0 deletions

diff --git a/cask/util/src-jvm/cask/util/Scheduler.scala b/cask/util/src-jvm/cask/util/Scheduler.scala
new file mode 100644
index 0000000..74db37e
--- /dev/null
+++ b/cask/util/src-jvm/cask/util/Scheduler.scala
@@ -0,0 +1,16 @@
+package cask.util
+
+import java.util.concurrent.{Executors, TimeUnit}
+
+object Scheduler{
+  val scheduler = Executors.newSingleThreadScheduledExecutor()
+  def schedule(millis: Long)(body: => Unit) = {
+    scheduler.schedule(
+      new Runnable {
+        def run(): Unit = body
+      },
+      millis,
+      TimeUnit.MILLISECONDS
+    )
+  }
+}
\ No newline at end of file