- 01 Nov, 2013 3 commits
-
-
Erik Hugne authored
As TIPC transport for 0MQ will only work on post 3.8 Linux kernels where nonblocking connect was added, we add AC_RUN test to check for this functionality. Should the test fail, tipc is excluded from build/test. Signed-off-by:
Erik Hugne <erik.hugne@ericsson.com>
-
Erik Hugne authored
The tests are identical to the TCP ones, only the addressing is changed. Signed-off-by:
Erik Hugne <erik.hugne@ericsson.com>
-
Mark Barbisan authored
Shorten ZMQ_ROUTER_REASSIGN_IDENTITIES to ZMQ_ROUTER_HANDOVER. Also, added a test for the HANDOVER functionality.
-
- 29 Oct, 2013 2 commits
-
-
Richard Newton authored
-
Matt Connolly authored
-
- 28 Oct, 2013 2 commits
-
-
Pieter Hintjens authored
* The ZMQ_ROUTER_RAW API was deprecated in favor of ZMQ_STREAM * Same issue hit router.cpp, which I've fixed
-
MinRK authored
-
- 18 Oct, 2013 1 commit
-
-
Laurent Alebarde authored
-
- 04 Oct, 2013 1 commit
-
-
Brandon Carpenter authored
See issue 567.
-
- 26 Sep, 2013 1 commit
-
-
Pieter Hintjens authored
* Tests dealer-to-router connection 100 times * This was failing in ZMQ v4.0.0 RC1
-
- 20 Sep, 2013 2 commits
-
-
Pieter Hintjens authored
* ZMQ_REQ_STRICT was negative option (default 1) which goes against the standard, where defaults are zero. I renamed this to ZMQ_REQ_RELAXED. * ZMQ_REQ_REQUEST_IDS felt clumsy and describes the technical solution rather than the problem/requirement. I changed to ZMQ_REQ_CORRELATE which seems more explicit.
-
Pieter Hintjens authored
* The ZMQ_CONNECT_DELAY option was renamed to ZMQ_IMMEDIATE
-
- 19 Sep, 2013 1 commit
-
-
Pieter Hintjens authored
-
- 12 Sep, 2013 1 commit
-
-
Richard Newton authored
-
- 11 Sep, 2013 1 commit
-
-
Richard Newton authored
-
- 10 Sep, 2013 1 commit
-
-
Richard Newton authored
-
- 04 Sep, 2013 5 commits
-
-
Pieter Hintjens authored
- tests that system can provide at least 1,000 sockets - we could expand on this but this covers the main case of OS/X having a too-low default limit of 256 handles per process
-
MinRK authored
rather than pretending it passes
-
Pieter Hintjens authored
-
Pieter Hintjens authored
* Command names changed from null terminated to length-specified * Command frames use the correct flag (bit 2) * test_stream acts as test case for command frames * Some code cleanups
-
Pieter Hintjens authored
-
- 02 Sep, 2013 1 commit
-
-
Pieter Hintjens authored
- 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 :-)
-
- 01 Sep, 2013 2 commits
-
-
Matt Connolly authored
-
MinRK authored
tests that default LINGER (-1) ensures message delivery. Note: it fails for large messages ( > 1MB, depending on the system).
-
- 19 Aug, 2013 1 commit
-
-
danielkr authored
-
- 03 Aug, 2013 1 commit
-
-
Christian Kamm authored
It defaults to enabled. Switch it off to be able to send a new message before the previous reply has been received.
-
- 28 Jul, 2013 1 commit
-
-
Christian Kamm authored
This allows making a new request on a REQ socket by sending a new message. Without the option set, calling send() after the first message is done will continue to return an EFSM error. It's useful for when a REQ is not getting a response. Previously that meant creating a new socket or switching to DEALER.
-
- 26 Jul, 2013 1 commit
-
-
Christian Kamm authored
* Documentation: The default behavior of REQ sockets is to rely on the ordering of messages to match requests and responses and that is usually sufficient. When this option is set to 1, the REQ socket will prefix outgoing messages with an extra frame containing a request id. That means the full message is (request id, 0, user frames...). The REQ socket will discard all incoming messages that don't begin with these two frames. * Behavior change: When a REQ socket gets an invalid reply, it used to discard the message and return EAGAIN. REQ sockets still discard invalid messages, but keep looking at the next one automatically until a good one is found or there are no more messages. * Add test_req_request_ids.
-
- 05 Jul, 2013 1 commit
-
-
Christian Kamm authored
-
- 02 Jul, 2013 1 commit
-
-
Christian Kamm authored
* See http://rfc.zeromq.org/spec:28/REQREP * Not all testable statements are covered. * At this point, there are several failures: - test_spec_req: The REQ socket does not correctly discard messages from peers that are not currently being talked to. - test_spec_dealer/router: On disconnect, the queues seem to not be emptied. The DEALER can still receive a message the disconnected peer sent, the ROUTER can still send to the identity of the dis- connected peer.
-
- 28 Jun, 2013 1 commit
-
-
Pieter Hintjens authored
RFC23, RFC24, RFC26 now use variable-length command names that end in null octet (valid C strings) instead of fixed-length space padded strings.
-
- 27 Jun, 2013 1 commit
-
-
Pieter Hintjens authored
- designed for TCP clients and servers - added HTTP client / server example in tests/test_stream.cpp - same as ZMQ_ROUTER + ZMQ_ROUTER_RAW + ZMQ_ROUTER_MANDATORY - includes b893ce set ZMQ_IDENTITY on outgoing connect - deprecates ZMQ_ROUTER_RAW
-
- 22 Jun, 2013 1 commit
-
-
Ian Barber authored
Test is skipped if no libsodium. Added warning if libsodium not configured
-
- 05 Jun, 2013 2 commits
-
-
Pieter Hintjens authored
- renamed to ZMQ_PROBE_ROUTER
-
Pieter Hintjens authored
- Cleaned up man page a little - Wrote test case tests/test_router_probe.cpp
-
- 15 May, 2013 1 commit
-
-
Pieter Hintjens authored
* ZMQ_PLAIN_SERVER, ZMQ_PLAIN_USERNAME, ZMQ_PLAIN_PASSWORD options * Man page changes to zmq_setsockopt and zmq_getsockopt * Man pages for ZMQ_NULL, ZMQ_PLAIN, and ZMQ_CURVE * Test program test_security
-
- 27 Apr, 2013 1 commit
-
-
Pieter Hintjens authored
-
- 25 Apr, 2013 1 commit
-
-
Jon Dyte authored
1) VSM - you cannot hand out the 'data' address as it was not allocated on the heap 2) for other messages the 'data' address cannot be handed out either, as it not the address originally returned by malloc and hence cannot be passed to 'free'. see msg.cpp u.lmsg.content = (content_t*) malloc (sizeof (content_t) + size_); .... u.lmsg.content->data = u.lmsg.content + 1; So the function is changed to always malloc a data buffer and copy the data into it. There is a possible optimisation using memmove for the non-VSM case but that is not done yet.
-
- 07 Feb, 2013 1 commit
-
-
montoyaedu authored
-
- 31 Jan, 2013 1 commit
-
-
Pieter Hintjens authored
-