mmehr2
commented
6 years ago There is code in place to time parts of the script transfer, but we may need to time the overall send operation with a reverse message (S>P) that specifies the time between the initial F command and the final load complete from the rich edit control.
Or we could instead time most of this on the Primary by updating a completion value after each message is sent out (publish replies), but it would not include time to load the text into the control on the secondary (or the final block if we load as we go).
This is about an optional enhancement. It may not be needed if script transfer is "fast enough".
Current plan is to have the Primary user enter edits (as asked by the talent at the Secondary end in an ongoing voice link). When Scrolling starts, the entire script will be sent at the start. If it turns out this takes too long, or is unacceptable for other reasons, we may want to capture the edits and send them individually over the net.
The ease of implementing this would depend a lot on how easy it is to capture all the relevant info for each kind of edit, and then how to send this in protocol messages.
I believe this can be left as OPTIONAL work, for if and when it proves that the script transfer is unacceptably slow.