put LevelUP() into closure

refactor this._status to variable in closure for cleaner code
comment out all sqlite3 benchmarks
jshint one "trailing":true is enough
code style tweaks
Merge pull request #1 from rvagg/ralphtheninja-master

code style tweaks
Merge pull request #62 from ralphtheninja/master

lib/levelup.js in closure
swap bufferstream for simple-bufferstream
Merge branch 'master' of github.com:rvagg/node-levelup
_location -> location exposed as read-only
version bump for @0.5.3
fix typo in contributors section
move encodingOpts levelup.js -> util.js
remove useBatch in copy
fix put/batch bug in WriteStream#_process()
InitializationError -> InitError to reduce line lengths
Revert "InitializationError -> InitError to reduce line lengths"

This reverts commit a0a1d78db4d6e0c4b7e59b284defcbe535e07ecf.
remove CloseError

The final else case in LevelUP#close() corresponds to the status
'new', which is the state the database has after the constructor
has been called. Since we always call LevelUP#open() before
returning the database object, it's impossible for the user to
call close() while the database is in the state 'new'. Therefore
the CloseError() can never happen.
Merge pull request #70 from rvagg/feature/rm-close-error

remove CloseError
ensure iterator end & next don't conflict

Race condition possible when you have a next() executing but end() is
also called. In the main JS thread we can create a barrier to protect
against this condition.
add test-10k-times.sh script