summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2012-07-03 18:11:10 -0400
committerGravatar Joey Hess <joey@kitenet.net>2012-07-03 18:11:10 -0400
commitf40b78d1254302f0ecab04ca4331e1048b178190 (patch)
tree53c8aa02d588ffd1654f1fc7bc515ef715c8f8a8
parenta6e267eeec9884441e8834c557c38bd0b7c1a5c1 (diff)
blog for the day
-rw-r--r--doc/design/assistant/blog/day_23__transfer_watching.mdwn25
1 files changed, 25 insertions, 0 deletions
diff --git a/doc/design/assistant/blog/day_23__transfer_watching.mdwn b/doc/design/assistant/blog/day_23__transfer_watching.mdwn
new file mode 100644
index 000000000..beaf75bc5
--- /dev/null
+++ b/doc/design/assistant/blog/day_23__transfer_watching.mdwn
@@ -0,0 +1,25 @@
+Starting to travel, so limited time today.
+
+Yet Another Thread added to the assistant, all it does is watch for changes
+to transfer information files, and update the assistant's map of transfers
+currently in progress. Now the assistant will know if some other repository
+has connected to the local repo and is sending or receiving a file's
+content.
+
+This seemed really simple to write, it's just 78 lines of code. It worked
+100% correctly the first time. :) But it's only so easy because I've got
+this shiny new inotify hammer that I keep finding places to use in the
+assistant.
+
+Also, the new thread does some things that caused a similar thread (the
+merger thread) to go into a MVar deadlock. Luckily, I spent much of
+[day 19](day_19__random_improvements) investigating and fixing that
+deadlock, even though it was not a problem at the time.
+
+So, good.. I'm doing things right and getting to a place where rather
+nontrivial features can be added easily.
+
+--
+
+Next up: Enough nonsense with tracking tranfers... Time to start actually
+transferring content around!