How to organize work with sockets in applications?

Question

Mobile development

Hello.

We are going to change data transfer in applications (iOS, Android) from requests to Sockets. What are the practices for dealing with sockets on the client side? For now, I imagine it this way: all incoming events are sorted out by one manager, which, after processing the received data (if necessary), sends a Broadcast message (for example, via NSNotificationCenter in iOS), and those who subscribe to them themselves figure out what to do with them, with it makes no difference who sent the message to the server and whether it was sent at all (as happens in normal requests).
What other options are there?