You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For documents that can't delay load this is not problematic. But for those that can, like flow-view, it's a big perf hit (seconds).
This was simpler when prepare existed because the runtime would await the sequence being fully loaded before inbounding new ops (it would still allow outbound). In the updated world the sequence will need to be able to handle ops for segments it has not yet loaded.
The text was updated successfully, but these errors were encountered:
This change enabled partial load of sequences when the configuration option sequenceInitializeFromHeaderOnly is set to true.
When this is set to true, we load the header, and then return from the load core call after the header is loaded. While the body is loading we cache all incoming an outgoing ops. Once the body is loaded we apply the incoming ops, and then resubmit the outgoing ops.
Fixes#89
Previously the sequence would become active after only loading the header.
But a recent change waited on body load prior to giving access https://github.com/microsoft/Prague/blob/12c12a3bea16181fd478ea22dd8f04a01b327338/packages/runtime/sequence/src/sequence.ts#L612.
For documents that can't delay load this is not problematic. But for those that can, like flow-view, it's a big perf hit (seconds).
This was simpler when prepare existed because the runtime would await the sequence being fully loaded before inbounding new ops (it would still allow outbound). In the updated world the sequence will need to be able to handle ops for segments it has not yet loaded.
The text was updated successfully, but these errors were encountered: