Problem: client can use meaningless timeout
Problem: client can use meaningless timeout

If client heartbeat is same as, or higher than server connection timeout,
clients cannot work properly. Since client heartbeat is currently fixed
at 1000 msec, server timeout makes no sense below about 2 seconds.

Solution: fix to minimum 2000 msec (or zero, meaning no timeout).

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