nsqd: message timestamps should be nano
nsqd/nsqlookupd: remove global state
Merge pull request #232 from mreiferson/nanotime_232

nsqd: message timestamps should be nano
Merge pull request #234 from mreiferson/state_234

nsqd/nsqlookupd: remove global state
update changelog
docs: update all docs to point to new documentation home
Merge pull request #235 from mreiferson/new_docs_235

docs: point everything at new documentation home
nsqd: fix cleanup of Channel.messagePump on delete

when a channel is deleted that has clients and is actively
delivering messages it is possible that messagePump()
will block on its go channel write to clientMsgChan due to
race between that write and the exiting of all clients subscribed
to that channel.

if that happens, the messagePump for the deleted channel
never exits and a reference is retained preventing the
channel from being GCd.
nsqd: discard old channel references

when the channels for a topic *shrinks* we weren't
correctly discarding the pointer to the deleted
channel
support full range of HTTP pprof profiling
Merge pull request #238 from mreiferson/debug_238

nsqd: support full range of HTTP pprof endpoints
Merge pull request #237 from mreiferson/leak_237

nsqd: memory leaks
persist nsqd metadata on topic/channel change
Merge pull request #231 from jehiah/persist_metadata_231

nsqd meta-data file writes pre/post being shut down uncleanly
update changelog and readme
nsqd: more context cleanup
Merge pull request #240 from mreiferson/more_context_240

nsqd: more context cleanup
fix wording
nsqd: dont alloc huge backing array for HTTP /mput

if a message is kept around (inflight, deferred, etc.)
and was part of a large /mput, the entire backing
array for that message body's slice was being retained
(preventing it from being GCd).

fix by refactoring /mput so that messages are allocated in
separately read chunks.

also, while in here make /mput atomic by validating
all messages up front before pushing to the topic.
(matching TCP MPUB behavior)
nsqd: dont retain client pointer for inflight msgs

more cleanup relating to what pointers might be retained
preventing proper GC.

this changes the in-flight messages struct so that it
uses an int64 ID rather than a pointer to ensure
that only the original receiver of a message can
respond to it.  this required changes to the channel
to store clients as a map[int64]Consumer in order
to lookup the proper client by ID.