Enable session multiplexing by default

[sync-by-unito]

It's more efficient and both the server and the client support it, so it makes sense to have it on by default. It will simplify the API and allow us to remove the section from the docs.

[sync-by-unito]

➤ Brian Munkholm commented:

[~nikola.irinchev] Is this still relevant?

[sync-by-unito]

➤ Nikola Irinchev commented:

Yes.

[sync-by-unito]

➤ Brian Munkholm commented:

Should be trivial. Any reasons not to do this?

[sync-by-unito]

➤ Jonathan Reams commented:

I'm not sure what the impact on our testing this will have, but we can take a look at whether this is a good idea next quarter.

[sync-by-unito]

➤ Jonathan Reams commented:

I was working on enabling this and ran into issues with the server, but now I can't find anywhere that its exposed from an SDK. What API and docs are getting simplified by doing this?

[sync-by-unito]

➤ Nikola Irinchev commented:

This is the JS API: https://github.com/realm/realm-js/blob/7f86a86d68eb2f95a18cb3613772c7f1c3b2c965/docs/sync.js#L280-L289

If the server doesn't support multiplexing, then we should just remove the API from Core and mark this as deprecated.