react/features/file-sharing/constants.ts

/**
 * The key prefix for file sharing metadata in the conference.
 */
export const FILE_SHARING_PREFIX = 'files';
feat(file-sharing) add support for file sharing Co-authored-by: Saúl Ibarra Corretgé <saghul@jitsi.org> Co-authored-by: Lucian-Paul Torje <lucian-paul.torje@8x8.com> 2025-04-09 10:44:17 +03:00			`/**`
fix(file-sharing) rework sync Rework sync so uploading multiple files at once or several moderators uploading files simultaneously doesn't break synchronization. The current room metadata plugin operates on <key,value> pairs and we were using a generic "files" key and using a nested object as our value. Since with every operation the entire object is replaced it's easy to get out of sync because one needs to be sure to have the full state before overwriting it. This is not realistic. We'll look into making the metadata plugin more flexible in order to support add / delete operations also on nested objects, but for the time being the following will suffice: Use a key prefix, so each file has en entry in the room metadata, like so: "files.<the file ID> -> file metadata". This means that when a file is deleted we just empty the metadata. The metadata plugin doesn't currently support removing existing keys. 2025-05-22 11:18:32 +02:00			`* The key prefix for file sharing metadata in the conference.`
feat(file-sharing) add support for file sharing Co-authored-by: Saúl Ibarra Corretgé <saghul@jitsi.org> Co-authored-by: Lucian-Paul Torje <lucian-paul.torje@8x8.com> 2025-04-09 10:44:17 +03:00			`*/`
fix(file-sharing) rework sync Rework sync so uploading multiple files at once or several moderators uploading files simultaneously doesn't break synchronization. The current room metadata plugin operates on <key,value> pairs and we were using a generic "files" key and using a nested object as our value. Since with every operation the entire object is replaced it's easy to get out of sync because one needs to be sure to have the full state before overwriting it. This is not realistic. We'll look into making the metadata plugin more flexible in order to support add / delete operations also on nested objects, but for the time being the following will suffice: Use a key prefix, so each file has en entry in the room metadata, like so: "files.<the file ID> -> file metadata". This means that when a file is deleted we just empty the metadata. The metadata plugin doesn't currently support removing existing keys. 2025-05-22 11:18:32 +02:00			`export const FILE_SHARING_PREFIX = 'files';`