summaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorNick White <hg@njw.me.uk>2011-08-03 00:34:35 +0100
committerNick White <hg@njw.me.uk>2011-08-03 00:34:35 +0100
commitbbce84ba6c4b7a208bf872e553abc98ed2ecfa20 (patch)
tree06cbe583c552d458ba03c061e384672c6849840c /TODO
parent6b8f282b5b0c0621ebcf6124f6a6cb90fed47297 (diff)
Flush -p stdout per line
Diffstat (limited to 'TODO')
-rw-r--r--TODO6
1 files changed, 5 insertions, 1 deletions
diff --git a/TODO b/TODO
index a1acd78..6aaf198 100644
--- a/TODO
+++ b/TODO
@@ -1,3 +1,7 @@
+got a stack trace when a connection seemingly timed out (after around 30 successful calls to -p)
+
+getgmissing doesn't work brilliantly with preview books as it will always get 1st ~40 pages then get ip block. getgfailed will do a better job
+
list all binaries in readme and what they do
# other utils
@@ -28,4 +32,4 @@ to be fast and efficient it's best to crank through all the json 1st, filling in
this requires slightly fuller json support
could consider making a json reading module, ala confoo, to make ad-hoc memory structures from json
-Note: looks like google allows around 3 page requests per cookie session, and about 40 per ip per [some time period]. If I knew the time period, could make a script that gets all it can, gets a list of failures, waits, then tries failures, etc. Note these would also have to stop at some point; some pages just aren't available
+Note: looks like google allows around 3 page requests per cookie session, and exactly 31 per ip per [some time period]. If I knew the time period, could make a script that gets all it can, gets a list of failures, waits, then tries failures, etc. Note these would also have to stop at some point; some pages just aren't available