simplify change publish options (#879)

* simplify change publish options

* better comments

Author: thesyncim

protobuf/video/sfu/event/events.pb.go

@@ -77,15 +77,14 @@ message SfuEvent {
     ParticipantUpdated participant_updated = 24;
     // ParticipantMigrationComplete is sent when the participant migration is complete
     ParticipantMigrationComplete participant_migration_complete = 25;
-    // ChangePublishOptionsComplete is sent to signal the completion of a ChangePublishOptions request.
-    ChangePublishOptionsComplete change_publish_options_complete = 26;
     // ChangePublishOptions is sent to signal the change in publish options such as a new codec or simulcast layers
     ChangePublishOptions change_publish_options = 27;
   }
 }
 
 message ChangePublishOptions {
-  models.PublishOption publish_option = 1;
+  repeated models.PublishOption publish_option = 1;
+  string reason = 2;
 }
 
 message ChangePublishOptionsComplete {

protobuf/video/sfu/event/events.proto

@@ -142,6 +142,20 @@ message PublishOption {
   // - Half resolution (2 layers) = 640x360
   // - Quarter resolution (3 layers) = 320x180
   VideoDimension video_dimension = 7;
+
+  // The unique identifier for the publish request.
+  // - This `id` is assigned exclusively by the SFU. Any `id` set by the client
+  //   in the `PublishOption` will be ignored and overwritten by the SFU.
+  // - The primary purpose of this `id` is to uniquely identify each publish
+  //   request, even in scenarios where multiple publish requests for the same
+  //   `track_type` and `codec` are active simultaneously.
+  //   For example:
+  //     - A user may publish two tracks of the same type (e.g., video) and codec
+  //       (e.g., VP9) concurrently.
+  // - This uniqueness ensures that individual requests can be managed
+  //   independently. For instance, an `id` is critical when stopping a specific
+  //   publish request without affecting others.
+  int32 id = 8;
 }
 
 message Codec {