- if ZAP server returns anything except 200, connection is closed
- all security tests now pass correctly
- test_security_curve now does proper client key authentication using test key
- test_security_plain now does proper password authentication

- Split off NULL security check from PLAIN
- Cleaned up test_linger code a little
- Got all tests to pass, added TODOs for outstanding issues
- Added ZAP authentication for NULL test case
- NULL mechanism was not passing server identity - fixed
- cleaned up test_security_plain and removed option double-checks (made code ugly)
- lowered timeout on expect_bounce_fail to 150 msec to speed up checks
- removed all sleeps from test_fork and simplified code (it still passes :-)

add test_linger

Adding ability for a context to be terminated in a forked child process

Remove delay options

avoids -Wall failures comparing int to uint

test failed auth for both PLAIN and CURVE

Terminate context in a child process of fork() to replace file descriptors to not interfere with parent process's context

tests that default LINGER (-1) ensures message delivery.

Note: it fails for large messages ( > 1MB, depending on the system).

Change name of icanhasall to subscribe_to_all

icanhasall is cute (for now), but the effect of the variable is clear
only after tracking down its origin reading the commit. This change is
intended to make it easier for people to have some intuition about its
effect from its name.

adds expect_bounce_fail test function

which is like bounce, but fails if messages arrive.

This test fails because PLAIN authentication doesn't actually reject connections

Disable failing tests on windows.

Fixed silly port number.

Fixed markup so documentation can be built.

get to clean compile under vs2012

Added some missing (but existing in branch) files to libzmq11 project needed
to compile as static library by VS2012 (at least), and fixed some warnings.
One warning remains in raw_decoder.cpp, which I'm leaving for now because I'm
not sure how project owners would like to fix it.

Add the Socket Identity info to the ZAP Messages

Add ZMQ_CONFLATE socket option

This change adds the socket identity infomartion from the socket to the
zap frames.  In doing this the ZAP is able preform different operations
based on different sockets.  This is not compaitable with the current ZAP
RFC, but that can be updated.  As the ZAP rfc is currently draft for I
did not change the version number.

Tests also modified and passing.

Minor doc & assert fixes

Optimized zmq::msg_t for constant messages

These were exposed to users, but have subsequently been removed as
sockopts. They are currently only being used by ZAP, so I've moved it to
a simpl function call (actually it's only used in one case even in that,
so there may be a further simplification possible there).