cheykrym/socket.io-client-swift
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add more to the migration guide

Browse Source
This commit is contained in:
Erik Little 2017-11-12 11:22:26 -05:00
parent 3595662729
commit 5c9dc2cee8
No known key found for this signature in database
GPG Key ID: 4930B7C5FBC1A69D
1 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
Usage Docs/12to13.md
View File

@ -34,12 +34,19 @@ let namespaceSocket = manager.socket(forNamespace: "/swift")
In v13 `defaultSocket` and `namespaceSocket` will share a single transport. This means one less connection to the server In v13 `defaultSocket` and `namespaceSocket` will share a single transport. This means one less connection to the server
needs to be opened. needs to be opened.
## What do I have to change? ## What might I have to change?
The most obvious thing you will need to change is that instead of creating `SocketIOClient`s directly, you will create a - The most obvious thing you will need to change is that instead of creating `SocketIOClient`s directly, you will create a
`SocketManager` and either use the `defaultSocket` property if you don't need namespaces, or call the `SocketManager` and either use the `defaultSocket` property if you don't need namespaces, or call the
`socket(forNamespace:)` method on the manager. `socket(forNamespace:)` method on the manager.
- `SocketIOClient` is no longer a client to an engine. So if you were overriding the engine methods, these have been moved
to the manager.
- The library is now a single target. So you might have to change some of your Xcode project settings.
- `SocketIOClient`s no longer take a configuration, they are shared from the manager.
---------- ----------
# What things should I know? # What things should I know?