Martin Georgiev

Handle case where client time has drifted further than 500ms after we have saved the server time offset

2

It's a continuation of spec item ([RSA4b1](https://docs.ably.io/client-lib-development-guide/features/#RSA4b1)). Once we have saved the server time we should check if the client time hasn't drifted further. In this case we should call...

Make Realtime channels implement IObservable for messages and state changes

2

This will allow developers to easily use Rx.Net and simplify the workflow for consuming messages.

Replace static code analysis to use `Microsoft.CodeAnalysis.NetAnalyzers` instead of FxCop

1

The FxCop and Microsoft.CodeAnalysis.Analyzers are now deprecated. We should move to using Microsoft.CodeAnalysis.NetAnalyzers and moving the rules into .editorconfig which will help IDEs enforce the rules too. The migration is...

Currently we return an error code of 0 if PublishAsync doesn't complete in 10 seconds. However the error code and status code passed back to the client is 0 so...

Refactor how we handle AblyAuth.ClientId

2

Currently the ClientId just delegates to a number of other internal properties like `ConnectionClientId`, `CurrentToken.ClientId`, `CurrentTokenParams.ClientId`. Which was all good until we needed to know when the `ClientId` has changed....

## Expected Behavior Using the following code I would except to either receive a buffer or a base64 encoded string. ``` const result = await client.binding.send('filestore', 'get', null, { blobName:...