From 3cc37a9dd973a9d5db20944b5c06af3fa27694ad Mon Sep 17 00:00:00 2001 From: Nick White Date: Thu, 29 Sep 2011 19:28:51 +0100 Subject: Update TODO and README now getabook is good --- README | 1 - TODO | 8 ++------ 2 files changed, 2 insertions(+), 7 deletions(-) diff --git a/README b/README index 2c89031..7137879 100644 --- a/README +++ b/README @@ -4,7 +4,6 @@ getxbook is a collection of tools to download books from websites. * getgbook - downloads from google books' "book preview" * getabook - downloads from amazon's "look inside the book" - (coming soon) * getbnbook - downloads from barnes and noble's "book viewer" (coming soon) diff --git a/TODO b/TODO index b62f90b..dad013d 100644 --- a/TODO +++ b/TODO @@ -1,8 +1,4 @@ -before 1.0: create other 2 utilities, fix http bugs, be unicode safe, package for osx & windows - -# getabook - -not all pages of 0312607172 are got, though they're available from web interface. maybe cookies are needed after all :( +before 1.0: create bn tool, fix http bugs, be unicode safe, package for osx & windows # getbnbook @@ -16,7 +12,7 @@ use wide string functions when dealing with stuff returned over http; it's known this means c99, rather than plain ansi c. worth it. alternative is to just use our own bit of utf-8 handling; we only need to know to skip x number of bytes to get one char at a time, to find next char etc. whether this would get more tricky, being unable to use strcmp etc, to make it not worthwhile, is not yet certain. try it and see if it fits. note st has nice homemade utf8 support. -bug in get(): if the \r\n\r\n after http headers is cut off between recv buffers +bug in get() & post(): if the \r\n\r\n after http headers is cut off between recv buffers what happens if we receive not a http header? does recv loop forever, in a memory killing manner? -- cgit v1.2.3