Hi all, As you may know we're drafting a new protocol for tcp://.
The current draft is here: http://rfc.zeromq.org/spec:23, and libzmq already implements most of that (NULL and PLAIN mechanisms). We just merged a patch from Martin Hurton to do ZAP authentication (http://rfc.zeromq.org/spec:27). I'd like to raise awareness of this work and get input on things we should add now to ZMTP. Libzmq is no longer the only stack implementing this protocol. Here is what's changed in 3.0: * clearer version numbering & negotiation * extensible security mechanisms (allowing encryption and authentication) * "resources" for endpoints, allowing port sharing * extensible meta-data for connection Here are some things I'd like to explore: * heartbeating, to detect stopped connections * recovery strategy for REQ-REP sockets If there's no debate, what will happen is gradual improvement over time, which is fine. However this is a great moment to get involved, if you care about this transport layer. -Pieter _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
