Problem: expiry timers are not scalable for many clients
Problem: expiry timers are not scalable for many clients

See https://gist.github.com/hintjens/795ddedd577e3e0f00fc

Solution: use tickets instead of timers. I've not tested the
performance change in zproto_server yet, just simulated it with
the above test case, and ensure that nothing has broken so far.

I'd be very interested in any results from people with the
infrastructure to test hundreds or thousands of clients.

hintjens/zproto,zeromq/zproto,jdiez17/zproto,asokoloski/zproto,asokoloski/zproto,c-rack/zproto,c-rack/zproto,vyskocilm/zproto,jemc/zproto,somdoron/zproto,bkmit/zproto,hintjens/zproto,hintjens/zproto,zeromq/zproto,zeromq/zproto,zeromq/zproto,c-rack/zproto,hintjens/zproto,sphaero/zproto,jdiez17/zproto,jemc/zproto,somdoron/zproto,sphaero/zproto,zeromq/zproto,bkmit/zproto,jdiez17/zproto,sphaero/zproto,hintjens/zproto,asokoloski/zproto,jdiez17/zproto,vyskocilm/zproto,bkmit/zproto,jemc/zproto,bkmit/zproto,jemc/zproto,jdiez17/zproto,sappo/zproto,hintjens/zproto,vyskocilm/zproto,jemc/zproto,c-rack/zproto,asokoloski/zproto,sphaero/zproto,sappo/zproto,asokoloski/zproto,vyskocilm/zproto,somdoron/zproto,c-rack/zproto,jdiez17/zproto,bkmit/zproto,bkmit/zproto,asokoloski/zproto,asokoloski/zproto,zeromq/zproto,sphaero/zproto,jdiez17/zproto,jemc/zproto,sappo/zproto,jemc/zproto,bkmit/zproto,somdoron/zproto,sappo/zproto,somdoron/zproto,hintjens/zproto,c-rack/zproto,somdoron/zproto,vyskocilm/zproto,sphaero/zproto,sappo/zproto,c-rack/zproto,vyskocilm/zproto,somdoron/zproto,sappo/zproto,zeromq/zproto,vyskocilm/zproto,sappo/zproto