sachin shinde
- Pool.completed is a unstable call. - When I use ```await pool.completed()```, I use all kind of memory related issues. - As a workaround, I am using ```await Promise.all()```
- Bumping up this issue again https://github.com/parallel-js/parallel.js/issues/119 - I couldn't find any documentation related to this, any insights will be really useful
Implement reconnection using exponential backoff and plain reconnection timout. Implement Pinging to server and ping timeout for detecting connection issues. Implement compression level data setting.
* Sync all socket level API's with respect to JS client * Sync all channel level API's with respect to JS client. * Well tested major release of client
Add support to connect asynchronously using async/await. Implement scclient using asynchronous streams, given in Rx.Net (Reactive extensions).
* Check implementation for [TM1](https://docs.ably.io/client-lib-development-guide/features/#TM1), [TM2](https://docs.ably.io/client-lib-development-guide/features/#TM2) and [TM3](https://docs.ably.io/client-lib-development-guide/features/#TM3) * Add missing tests for the same * Related to [this internal Slack discussion](https://ably-real-time.slack.com/archives/C0114KK7S6R/p1627377435245000) ┆Issue is synchronized with this [Jira Task](https://ably.atlassian.net/browse/SDK-1139) by...
* Related to comment https://github.com/ably/ably-go/pull/370#issuecomment-894395238 * Current logic can be improved for efficiency of encrypted data. ┆Issue is synchronized with this [Jira Task](https://ably.atlassian.net/browse/ECO-4426) by [Unito](https://www.unito.io)
Need to implement reconnection and auto channel subscribe for the client. Implement proper logging using https://github.com/sirupsen/logrus
* Sync all socket level API's with respect to JS client * Sync all channel level API's with respect to JS client. * Well tested major release of client
Asynchronous connect and observable stream support for client