Open vinomaster opened 13 years ago
Making my notes public:
Discussed this with Brian. We should review for importance knowing that it would be very useful for COPD app. Thoughts on design:
Can we not run op engine at viewer sites and have them take the last context vector from the last moderator to relinquish control to seed the context vector table for all sites as they all become editors again?
This is key to scaling.
Picking up where we left off. We need to start simple. Brian and I discussed simple as meaning:
On behalf of AliceZhang: There is a requirement to provide a mechanism to support 1 editor - m readers/observers scenario more efficiently, ie, do not store those events and do not go through OT engine.
For the 1 editor - n viewer case, it is easy to achieve the user experience by an application client, ie, the application client for a viewer will not send out any sync event. What we want to verify is that the approach/implementation you have meet the following requirements:
Thanks.
Current understanding is this is a optimization wish-list item, but not a hard requirement by Alice. Moving to next planned release.
Enhance Coweb API to support the ability to govern which users can broadcast events. When this support is toggled off all users (default) are allowed to broadcast. Otherwise, specific users are granted broadcast ability. All users get to see all events.