summaryrefslogtreecommitdiff
path: root/cask/util
Commit message (Collapse)AuthorAgeFilesLines
* Update WsClient.scalalihaoyi-patch-1Li Haoyi2019-09-191-0/+2
|
* Update WebsocketClientImpl.scalaLi Haoyi2019-09-191-1/+1
|
* Update WebsocketClientImpl.scalaLi Haoyi2019-09-191-1/+1
|
* Update WebsocketClientImpl.scalaLi Haoyi2019-09-191-1/+3
|
* Update WebsocketClientImpl.scalaLi Haoyi2019-09-191-1/+1
|
* Update WebsocketClientImpl.scalaLi Haoyi2019-09-191-3/+7
|
* Update WsClient.scalaLi Haoyi2019-09-191-2/+1
|
* Update WebsocketClientImpl.scalaLi Haoyi2019-09-191-2/+4
|
* Provide a simple builtin websocket client in `cask.WsClient`Li Haoyi2019-09-169-7/+194
| | | | | | 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
* cross-build cask.util for Scala.jsLi Haoyi2019-09-162-0/+58