summaryrefslogtreecommitdiff
path: root/doc/design/assistant/webapp.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2013-03-19 19:02:56 -0400
committerGravatar Joey Hess <joey@kitenet.net>2013-03-19 19:02:56 -0400
commitaef6d297681566c63a0c8b1b86dfb0f73b757669 (patch)
tree2b5357229df53a6b0bfd1130bfcda4201582d293 /doc/design/assistant/webapp.mdwn
parent166145bcba1a75baf45192517b3a90609c96867c (diff)
blog for the day
Diffstat (limited to 'doc/design/assistant/webapp.mdwn')
-rw-r--r--doc/design/assistant/webapp.mdwn9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/design/assistant/webapp.mdwn b/doc/design/assistant/webapp.mdwn
index 08e0a9b58..f9844e73c 100644
--- a/doc/design/assistant/webapp.mdwn
+++ b/doc/design/assistant/webapp.mdwn
@@ -1,5 +1,14 @@
The webapp is a web server that displays a shiny interface.
+## performance
+
+Having the webapp open while transfers are
+running uses significant CPU just for the browser to update the progress
+bar. Unsurprising, since the webapp is sending the browser a new `<div>`
+each time. Updating the DOM instead from javascript would avoid that;
+the webapp just needs to send the javascript either a full `<div>` or a
+changed percentage and quantity complete to update a single progress bar.
+
## other features
* there could be a UI to export a file, which would make it be served up