Fixed compile issue with missing member of socket_base.  Changed ZMQ_NEXT_IDENTITY to ZMQ_NEXT_CONNECT_PEER_ID.

Fixed case where ZMQ_NEXT_CONNECT_PEER_ID is used in ROUTER, and ROUTER does not read the identity message from the connected pipe.

Both STREAM and ROUTER sockets suffer from a naming problem on outbound connections. While these connections can be created, they can't be immediately used. Traffic must be received before it can be sent. This prevents practical, minimal usage of STREAM or ROUTER as a true N fan in/out socket.

This change simply provides the user with a socket option that sets a user defined name of the next outbound connection:

zmq_setsockopt(routerSock,ZMQ_NEXT_IDENTITY,"myname",6);
if(0 > zmq_connect(routerSock,"tcp://127.0.0.1:1234")) return 1;
ret = zmq_send(routerSock,"myname",6,ZMQ_SNDMORE);
zmq_send(routerSock,b.mem,b.used,0);

In this example, the socket is immediately given the name "myname", and is capable of immediately sending traffic.

This approach is more effective in three ways:
1) It prevents all sorts of malicious peer naming attacks that can cause undefined behavior in existing ROUTER connections. (Two connections are made that both transmit the same name to the ROUTER, the ROUTER behavior is undefined)
2) It allows immediate control of connections made to external parties for STREAM sockets. Something that is not possible right now. Before an outbound connection had no name for STREAM or ROUTER sockets because outbound connections cannot be sent to without first receiving traffic.
3) It is simpler and more general than expecting two ROUTER sockets to handshake on assigned connection names. Plus it allows inline sending to new connections on ROUTER.

fixed cmake merge related to version.rc.in handling

Corrects ypipe initialization when conflate is NOT enabled.

Fixes LIBZMQ-584

Adds support for detecting ZMQ_STREAM disconnections.

Fixes CMake build after ZAP test file was deleted.

File was removed in 5bf96f64 a few days ago.

When a ZMQ_STREAM socket connection is broken (intentionally, via `shutdown()`
or accidentally via client crash or network failure), there is no way for the
application to dertermine that it should drop per-connection data (such as
buffers).

This contribution makes sure the application receives a 0-length message to
notify it that the connection has been broken.  This is symmetric with the
process of closing the connection from within the application (where the
application sends a 0-length message to tell ZeroMQ to close the connection).

Conflicts:
	CMakeLists.txt

Define NOMINMAN to fix windows build.

use version-script only for ELF linux

Fix compilation on Windows (MinGW-w64)

Implement socket_base_t::get_credential member function

The get_credential () member function returns
credential for the last peer we received message for.
The idea is that this function is used to implement user-level API.

Only export zmq_* symbols

Fix timestamp counter on s390/s390x

Fixes #811

windows: changed tcp port from glrpc assigned to unassigned one

cmake: fixed error 'install TARGETS given no ARCHIVE DESTINATION'

Replace assert with zmq_assert

Fix some comments regarding method overriding

Make it explicit that the probe function doesn't modify passed message

ZMQ_SRCFD docs and tests

Also moved the fd field from message content to message itself

Simplify ypipe_t and ypipe_base_t template parameters

Allow clients to get remote endpoint per message for TCP connections