diff options
author | Li Haoyi <haoyi.li@databricks.com> | 2019-09-16 22:31:03 +0800 |
---|---|---|
committer | Li Haoyi <haoyi.li@databricks.com> | 2019-09-16 22:31:03 +0800 |
commit | bfe26d5a9705011359658c45b364e9b65ce697b5 (patch) | |
tree | 656565b3d147b1837d4cfc1d949e7af8c250f16c /build.sc | |
parent | 84ea971b1261919aca7b31635ddc7d0dca830fea (diff) | |
download | cask-bfe26d5a9705011359658c45b364e9b65ce697b5.tar.gz cask-bfe26d5a9705011359658c45b364e9b65ce697b5.tar.bz2 cask-bfe26d5a9705011359658c45b364e9b65ce697b5.zip |
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
Diffstat (limited to 'build.sc')
-rw-r--r-- | build.sc | 6 |
1 files changed, 6 insertions, 0 deletions
@@ -72,9 +72,15 @@ object cask extends CaskModule { object js extends UtilModule with ScalaJSModule{ def platformSegment = "js" def scalaJSVersion = "0.6.28" + def ivyDeps = super.ivyDeps() ++ Agg( + ivy"org.scala-js::scalajs-dom::0.9.7" + ) } object jvm extends UtilModule{ def platformSegment = "jvm" + def ivyDeps = super.ivyDeps() ++ Agg( + ivy"org.java-websocket:Java-WebSocket:1.4.0" + ) } } |