Properly close dead connections
authorJack Miller <jack@codezen.org>
Wed, 1 Jun 2016 02:47:03 +0000 (21:47 -0500)
committerJack Miller <jack@codezen.org>
Wed, 1 Jun 2016 02:47:03 +0000 (21:47 -0500)
commit872548c5d54569cf767ca4c7329ba155c1084bca
tree1a71bc25d6a54934317fe15691b61e8185147c96
parent52c038c54b81fb54c185788d1210f3ad9b1fb90a
Properly close dead connections

I'm a bit surprised I haven't caught this before, I guess I was relying
on garbage collection to destroy dead connections for me, but when you
do something like

$ while /bin/true; do canto-remote status; done

and create nonstop connection thrashing that's not good enough (if it
works at all), so explicitly call close().
canto_next/server.py