diff options
| author | Nick White <git@njw.me.uk> | 2011-09-29 19:28:51 +0100 |
|---|---|---|
| committer | Nick White <git@njw.me.uk> | 2011-09-29 19:28:51 +0100 |
| commit | 3cc37a9dd973a9d5db20944b5c06af3fa27694ad (patch) | |
| tree | 9635cd0a1f14942b3d8272d3864f1fa479167c1d /TODO | |
| parent | 6d992fbe0ee99dda0ec450d9d3f8941118414d37 (diff) | |
Update TODO and README now getabook is good
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 8 |
1 files changed, 2 insertions, 6 deletions
@@ -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? |