Lawrence Forooghian
Lawrence Forooghian
> Instead we check available plugins at runtime and throw an error if user tried to use an API that requires a plugin which was not provided. Would we want...
> Removing code related to realtime publishing I had a go at this in https://github.com/ably/ably-js/pull/1504 and we decided not to proceed with it since the bundle size reduction was disappointing....
I think we can close this issue.
I’m setting this as a medium priority but it’s a bit of a guess — I don't know how often the described scenario occurs in reality.
It seems like something we should implement; why would we close it?
I'll probably need to take some time to get some understanding of WebSockets in general (perhaps reading the RFC) before I can give this a proper review. I'll see if...
> Because this will replace core/critical functionality, it is probably a good idea to introduce it gradually via something like `clientOptions.useNativeWebSocket` and explicitly ask some clients to give it a...
@QuintinWillison: > So, perhaps, we should be discussing this as part of scope for version 2 of this SDK? (i.e. a `major` version bump) -- this should count as an...
Taking another look at this, in the context of [@umair-ably’s RFC for dropping support for iOS < 14](https://ably.atlassian.net/wiki/spaces/SDK/pages/2986147844/RFC+Deprecate+iOS+13+support+for+ably-cocoa). @maratal, do you remember whether your work here concluded that `NSURLSessionWebSocketTask` would...