2 ms·
How do you deal with network weights versioning? I assume the version that does the compressing and decompressing needs to match? And if you release an updat
by londons_explore 4y ago
How do you deal with network weights versioning?
I assume the version that does the compressing and decompressing needs to match? And if you release an update and half the users install it, this is a problem?
Do you have some mechanism to dynamically download and update weights to ensure that all users in a call at least have a common version of the network? Or will you just globally require all users to update before joining a call? (which in turn means every time you release an update, all calls must end, which isn't very enterprise-friendly)
- jacobgorm 4y agoGood question. The protocol is versioned, so you will be prompted to upgrade if/when I change the network doing the encoding/decoding. Downloading new weights on the fly should not be a problem (Apple would allow it as long as I don't change the code), but in many cases when evolving the protocol I've had to make changes to other parts of the code too, so not sure if it will be worthwhile.
- londons_explore 4y agoThinking about it... The obvious solution is to make every version support the current protocol and the previous protocol. You might sometimes have to downgrade a call sometimes if someone joins with an older client. Then anyone can join any call unless they are 2 or more versions behind.