Limit event count for ORA collaborative editing

Description

Using a collaborative editor model, we can have a very large number of events around sharing the state of the text response. Investigate ways to limit the number of events sent such that the Learner experience using the ORA is not degraded but the event count is controlled.

Consider: https://togetherjs.com/

Acceptance

  • Using Pusher, an ORA has a limited number of events used to describe the state of the text, such that the event count is much smaller than the net keystroke count.

  • Using the ORA in a group is still considered “Acceptable Lag”

Testing

  • Non-collaberative ORAs are not affected

  • Collaborative ORAs do achieve consistency between all editing Learners

  • Manual review of Pusher account shows increase in event count that matches test ORA activity

 

Steps to Reproduce

None

Current Behavior

None

Expected Behavior

None

Reason for Variance

None

Release Notes

None

User Impact Summary

None

Status

Assignee

Unassigned

Reporter

Matthew Carter

Labels

Reach

None

Impact

None

Platform Area

None

Customer

None

Partner Manager

None

URL

None

Contributor Name

None

Groups with Read-Only Access

None

Story Points

2

Actual Points

None

Category of Work

None

Platform Map Area (Levels 1 & 2)

None

Platform Map Area (Levels 3 & 4)

None

Epic Link

Sprint

Priority

Unset
Configure