add a new poller named pollset which will get benefit of performance in AIX platform.

add a new poller named pollset which will get benefit of performance in AIX platform.

Problem: zmq_connect with IPv6 "source:port;dest:port" format is broken

Solution: allow for '[' character when doing the basic sanity check
on the TCP endpoint.
Also add unit tests for both IPv4 and IPv6 source;dest format.

Solution: add them

Solution: add a test for this use case

Solution: add disconnect and unbind calls to the test

Solution: refactor it to allow for multiple functionalities to be
tested

Problem: source conatins tabs and trailing spaces

Solution: remove them

Solution: replace tabes with spaces

Problem: MinGW cross compile is failed on Linux

Solution: Use only lower case for header file name.

We can find "wincrypt.h" by "WinCrypt.h" on Windows because Windows uses
case insensitive file system. But we can't find "wincrypt.h" by
"WinCrypt.h" on Linux Because Linux uses case sensitive file system.

Problem: Missing newline in printf statement

Solution: Add "\n" at end of format string.

Problem: scoped optional mutex lock caused unit tests to fail

Solution: Add a scope that scopegurad unlocks the mutex
 before the object instance deletes itself and wants to unlock
a locked mutex

Problem: socket_base uses macros for mutex lock and unlock

Solution: add a lock guard that takes optional a mutex and use it

Problem: CMake build from dist tarball broken

Solution: include src/version.rc.in and tests/CMakeLists.txt in the
make dist tarball by adding them to makefile.am EXTRA_DIST list.

Problem: cannot build packages with DRAFT APIs

Solution: if rpmbuild is called with --with drafts, which can be
triggered on OBS by adding:
  Macros:
  %_with_drafts 1
to the bottom of the prjconf, then enable draft APIs.

Solution: parse the OBS prjconf and the user env variable
DEB_BUILD_OPTIONS. If either of those define "drafts" then build with
draft APIs enabled.

Fix building documentation

Solution: The regular expression replacement expected a non-existing
space at the beginning of the input files.

Solution: The CMAKE module PythonInterp sets the variable
PYTHONINTERP_FOUND and not PYTHON_FOUND if it finds
a python interpreter.

Problem: testutil.hpp fails to build on Windows XP

Solution: ifdef is_ipv6_available to always return false if building
on Windows XP, as it doesn't support the needed standard libc
functions

[gssapi] memory allocation mismatch on windows

The gssapi has some helper functions gssalloc_malloc()/gssalloc_free()
which on windows doesn't call malloc()/free(). Instead these are
wrappers around HeapAlloc() and HeapFree(). To complicate matters
gssapi doesn't export these helper functions, so you're left using
the allocation method of your choice.

See Here:
https://github.com/krb5/krb5/blob/89683d1f135765e91041f3a239af865b11aaf86b/src/lib/gssapi/generic/gssapi_alloc.h

The zmq gssapi implementation is calling malloc and then calling
gss_release_buffer() to free the memory. gss_release_buffer uses
gssalloc_free() to free this buffer which on windows calls HeapFree()
instead of free(). This causes an access violation on windows.

Problem: tests should not create 2 ZMQ contexts

Solution: call the function after the zmq_ctx has been created, not
before, so that the relevant Windows system calls have been setup.

This reverts commit 9adf20aa.

is_ipv6_available: Create a fake zmq context on windows

This is required as zmq_ctx_new calls WSAStartup. Without that the IPV6
socket creation always fails.

Fix compatibility with newer CMake.

Problem: zmq_stream doc is confusing regarding ZMQ_SNDMORE flag

Solution: fix it.

The documentation first states that the ZMQ_SNDMORE flag is ignored on
data frames. Then it states that omitting the ZMQ_SNDMORE flag has
consequences. The example HTTP server code further muddies the situation
with a similar comment.

The implementation of ZMQ_STREAM only accepts two-part messages.
The first part is an identity frame while the second and last part is
the data frame.

As with any multipart message, all parts except the last need the
ZMQ_SNDMORE flag. The second and last part would normally omit the
ZMQ_SNDMORE flag to mark the end of the multipart message.

However, the ZMQ_STREAM implementation ignores the ZMQ_SNDMORE flag on
the data frame rather than requiring that it be omitted. The latter
behaviour would have been more consistent with the other ZeroMQ
sockets.