Now room IDs and user IDs are arbitrary strings. Would be nice to fix unnecessary copying but this implementation should be OK for now.
For the moment, we continue to accept numeric JSON IDs in signalling messages; later, once client code is updated, we'll break backwards compatibility. This change does make the user IDs returned in signalling responses into strings, which could break client code, but ours is resilient to that (and since IDs are opaque and only good for comparing equality probably other code is also resilient to that.)
Now room IDs and user IDs are arbitrary strings. Would be nice to fix unnecessary copying but this implementation should be OK for now.
For the moment, we continue to accept numeric JSON IDs in signalling messages; later, once client code is updated, we'll break backwards compatibility. This change does make the user IDs returned in signalling responses into strings, which could break client code, but ours is resilient to that (and since IDs are opaque and only good for comparing equality probably other code is also resilient to that.)