- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Mon, 28 Mar 2022 14:56:50 +0000
- To: public-webrtc-logs@w3.org
> > Looking at the new PR, I think it is missing the forStorage handling, something like: > > > > * Add forStorage as parameter to the serialisation steps algorithm. > > * As first step of the algorithm, throw an exception if forStorage is set to true. I agree with @youennf here. > On the PR itself, I have quoted this part: > > > The introduction of these steps should omit mention of the forStorage argument if it is not relevant to the algorithm. > > It's taken from [here](https://whatpr.org/html/6523/structured-data.html#serializable-objects). I read it as "ignore this if it's not relevant." I think you're misinterpreting it. It says _"The introduction of these steps should omit mention of the forStorage argument if it is not relevant to the algorithm."_ which seems to say to not list the argument in the argument list unless it is referenced in the algorithm. Since the this algorithm would throw on it, that is satisfied. Cc-ing @annevk as the authority on what the intent as far as default behavior here is, if any. > Seems irrelevant enough to me. Or why do you think it's important to specify throwing? We should narrow the scope of functionality to what's necessary for the use cases we're solving. If we don't need to implement storage, we shouldn't. The iterative process for adding functionality, is we hear use cases that demand it, and then discuss adding it. It's easy to add more functionality later. What's hard is to remove it. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-region/pull/24#issuecomment-1080760075 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 28 March 2022 14:56:51 UTC