Fixed AUTHORS to reflect Git history
Problem: nodes don't rejoin properly after reconnect

There is something weird going on in libzmq, I think, and this still
needs to be investigated. Node A DEALER connects to node B ROUTER and
sends messages once a second, and then the network interface dies, and
then node A destroys its socket. Then it creates a new socket, connects
to same endpoint B, and sends one new message. The old messages do
arrive, but the new one does not.

Solution: (and this is a workaround), remove the peer if we get an
unexpected command from it. See zyre_node.c:599.

Fixes #200.
zyre.h was included twice
Was incorrectly reporting EXIT on half-ready peer
Merge pull request #202 from hintjens/master

Fixes including provisional fix for #200
Set ZMQ_ROUTER_HANDOVER on node inbox

Problem: was incorrectly taking old PING messages from disconnected
peer socket, and ignoring new HELLO commands. The previous fix was
to destroy the peer and retry. However that didn't address the real
problem.

Solution: set ZMQ_ROUTER_HANDOVER on the router socket, so that new
client connections always replace existing ones.

This appears to work properly; the test is to run several instances
of zpinger on a laptop connected to a WiFi network, then disable the
WiFi interface, and then re-enable it. zpinger should first report
that its peers have exited, and then that they reappear.
Merge pull request #204 from hintjens/master

Set ZMQ_ROUTER_HANDOVER on node inbox
Zyre logging system removed

This is a substantial change. The logging system has been removed,
firstly because it did not work as well as hoped, and second it
made Zyre more complex than necessary. If we need a ZeroMQ-based
logging system we should add it as a separate protocol. Zyre now
uses the zsys_xxx logging API, to send all log output to stdout
or to syslog (if enabled by the application).
Merge pull request #205 from hintjens/master

Zyre logging system removed