On Sat, Aug 17, 2013 at 12:04 AM, Zack Weinberg zackw@cmu.edu wrote:
- State transitions between reading and editing.
Reads on our projects (whether logged in or out) have very little data coming from the client and a lot being sent back to the client. When a page is saved or previewed (or even in during an edit with calls to the parsoid web service?) or file uploaded then suddenly there's more substantial traffic going from the client up to the projects.
This could be mitigated in part by chunking larger transmissions and sending them over time. Which we already do for some users with the upload wizard. (i.e. file uploads. we could expand that to cover more users) Those chunked transmissions could be then spread out over time and mixed in with transmissions of garbage when there's no pending chunk to send.
That may be OK from a UX perspective for file uploads (run in the background and let the user do other stuff while the upload runs) but I don't think people will want to wait for their edits (or previews!) to go through.
Also, we'd probably need an opt-out option for sending the garbage when idle and we'd have to research the potential impact on bandwidth bills/quotas. And maybe also impact on battery life??
(it couldn't be opt-in because the fact that you had opted in would itself be an indicator that you might be an editor.)
-Jeremy