==============================
==>  MORE PROFILING!
====>  MORE BENCHMARKING!
======>  MORE OPTIMISATIONS!
========>  SMARTER ALGORITHMS!
==============================

general:
 code is scruffy, maybe re-write?
 this hash type db is old hat, maybe go mad and try a totally new concept?

format:
 better collision resolution
 breathing space should be more "scientific"

sdb_make:
 use iovecs?
 error checking
 linked list -> linked list of arrays
 speed up the parser somehow..
 speed up collision resolution
 atomic db replace

sdb_dump:
 better error checking

sdb_stats:
 stats program giving breakdown of distances
 point out hash collisions
 work out how evenly the data is distributed in hash tables

sdb_query:
 support non-unique keys

api:
 allow pluggable hash
