-
Notifications
You must be signed in to change notification settings - Fork 29.8k
Open
Labels
P3Issues that are less important to the Flutter projectIssues that are less important to the Flutter projecta: pluginsSupport for writing, building, and running plugin packagesSupport for writing, building, and running plugin packagesc: API breakBackwards-incompatible API changesBackwards-incompatible API changesc: contributor-productivityTeam-specific productivity, code health, technical debt.Team-specific productivity, code health, technical debt.c: new featureNothing broken; request for a new capabilityNothing broken; request for a new capabilityc: performanceRelates to speed or footprint issues (see "perf:" labels)Relates to speed or footprint issues (see "perf:" labels)engineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.perf: app sizePerformance issues related to app size (binary/code size) or disk spacePerformance issues related to app size (binary/code size) or disk spaceperf: speedPerformance issues related to (mostly rendering) speedPerformance issues related to (mostly rendering) speedteam-engineOwned by Engine teamOwned by Engine teamtriaged-engineTriaged by Engine teamTriaged by Engine team
Description
There's a lot of complexity with having ring buffers and so forth, and they are a source of some confusion and bugs. We would benefit greatly from this being significantly simpler.
For use cases where a small ring buffer greater than 1 is appropriate, it seems like a sufficient solution is just to store all the relevant information in every message and send that.
For use cases where large amounts of information should be cached, it seems like a solution is to have the plugin do the caching and await a request.
We should see whether any plugins are making use of the ChannelBuffers control channel. If none are, that would be a good signal that we can just remove this. If some are, we should investigate what the use cases are.
Metadata
Metadata
Assignees
Labels
P3Issues that are less important to the Flutter projectIssues that are less important to the Flutter projecta: pluginsSupport for writing, building, and running plugin packagesSupport for writing, building, and running plugin packagesc: API breakBackwards-incompatible API changesBackwards-incompatible API changesc: contributor-productivityTeam-specific productivity, code health, technical debt.Team-specific productivity, code health, technical debt.c: new featureNothing broken; request for a new capabilityNothing broken; request for a new capabilityc: performanceRelates to speed or footprint issues (see "perf:" labels)Relates to speed or footprint issues (see "perf:" labels)engineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.perf: app sizePerformance issues related to app size (binary/code size) or disk spacePerformance issues related to app size (binary/code size) or disk spaceperf: speedPerformance issues related to (mostly rendering) speedPerformance issues related to (mostly rendering) speedteam-engineOwned by Engine teamOwned by Engine teamtriaged-engineTriaged by Engine teamTriaged by Engine team