summaryrefslogtreecommitdiff
path: root/src
AgeCommit message (Collapse)Author
2010-09-04Merge branch 'maint'Martin Lucina
* maint: zmq::select_t, zmq_poll(): assert if FD_SETSIZE reached zmq.h: Fix typo and use of C99 comment Conflicts: src/zmq.cpp
2010-09-04zmq::select_t, zmq_poll(): assert if FD_SETSIZE reachedMartin Lucina
Ensure that 0MQ does not attempt to call select() on more than FD_SETSIZE file descriptors.
2010-09-02Merge branch 'maint'Martin Sustrik
* maint: Prior to this patch prefix_tree asserts. Fix for signaler_t on HP-UX and AIX platforms Mikael Kjaer added to AUTHORS Conflicts: src/trie.cpp
2010-09-02Prior to this patch prefix_tree asserts.Jon Dyte
This is because as it adds the 255th element at a node it attempts to calculate the count member var which is an unsigned char via count = (255 -0) + 1; and pass the result to realloc. Unfortunately the result is zero and realloc returns null; the prefix_tree asserts. I have fixed it by making the count an unsigned short.
2010-09-02Fix for signaler_t on HP-UX and AIX platformsBernd Melchers
2010-09-01Merge branch 'maint'Martin Sustrik
* maint: Erasure of retired fd's in select.cpp causes an assertion in MSVC 2008 STL
2010-09-01Erasure of retired fd's in select.cpp causes an assertion in MSVC 2008 STLMikael Helbo Kjær
I was hitting an issue with an SCL enabled STL library in connection with the way select_t::loop was erasing retired fd's. The problem as identified by the SCL assertion was that by the time the iterator given to the erase method was called it was considered invalid by the library. I am not sure this isn't just a "quirk" of the MSVC STL library as the other code looks valid to me as well.
2010-09-01conflicts resolvedMartin Sustrik
2010-09-01sys transport introdced; inproc://log moved to sys://logMartin Sustrik
2010-09-01MSVC build fixedMartin Sustrik
2010-09-01context creates an inproc endpoint ('inproc://log') to distribute 0MQ's log ↵Martin Sustrik
messages
2010-09-01assert when pipe attaches to PUB socket in process of termination -- fixedMartin Sustrik
2010-09-01pipe being attached to the PAIR socket during its termination process is ↵Martin Sustrik
immediately asked to terminate itself
2010-09-01hangup when closing socket with no pipes attached -- fixedMartin Sustrik
2010-08-31naming cleanup: yarray->arrayMartin Sustrik
2010-08-31naming cleanup: zmq_encoder->encoder, zmq_decoder->decoderMartin Sustrik
2010-08-30OSX build fixed -- semaphore replaced by mutexMartin Sustrik
2010-08-30Issue 54 - socket_base.cpp:162 comparison errorMartin Sustrik
2010-08-28prefix_tree_t renamed to trie_tMartin Sustrik
2010-08-28swap's block size made into a compile-time parameterMartin Sustrik
2010-08-28msg_store_t renamed to swap_tMartin Sustrik
2010-08-28refactoring of pipe/swap interactionMartin Sustrik
2010-08-28terminology unified: revive->activateMartin Sustrik
2010-08-28bug in pipe deactivation fixedMartin Sustrik
2010-08-28zmq_poll: account for the fact that ZMQ_FD is edge-triggeredMartin Sustrik
2010-08-27assert on malformed messagesDhammika Pathirana
2010-08-27zmq_poll returns prematurely even if infinite timeout is set - fixedMartin Sustrik
2010-08-27forwarder and streamer devices handle multi-part messages correctlyJon Dyte
2010-08-26improved null checking in zmq_termIvo Danihelka
2010-08-25MSVC build fixedMartin Sustrik
2010-08-25elementary fixes to the named sessionMartin Sustrik
2010-08-25connecter object unregisters its fd correctlyMartin Sustrik
2010-08-25listener object unregisters its fd correctlyMartin Sustrik
2010-08-25sessions created by listerner are correctly shut downMartin Sustrik
2010-08-25added ZMQ_MAKE_VALGRIND_HAPPY compile-time optionMartin Sustrik
2010-08-25engine leak fixed; pgm compilation fixedMartin Sustrik
2010-08-25one more dezombification bug fixedMartin Sustrik
2010-08-25dezombification procedure fixedMartin Sustrik
2010-08-25engine termination on disconnect fixedMartin Sustrik
2010-08-25I/O object hierarchy implementedMartin Sustrik
2010-08-25zmq_poll(): Fix some corner casesMartin Lucina
Trying to optimize out the case where items_[i]. events is 0 would result in a bogus pollfds[i]. Similarly in the select()-based impl, while not strictly necessary it's better to get ZMQ_FD even if events is 0 since that detects ETERM and friends.
2010-08-25zmq_poll(): Rewrite to use ZMQ_FD/ZMQ_EVENTS pt2Martin Lucina
Rewrite the select()-based zmq_poll() implementation to use ZMQ_FD and ZMQ_EVENTS. Also fix some corner cases: We should not pollute revents with unrequested events, and we don't need to poll on ZMQ_FD at all if a pollitem with no events set was passed in.
2010-08-25Fix whitespaceMartin Lucina
Dunno where those <TAB>s came from...
2010-08-25zmq_poll(): Rewrite to use ZMQ_FD/ZMQ_EVENTS pt1Martin Lucina
Rewrite zmq_poll() to use ZMQ_FD and ZMQ_EVENTS introduced on the wip-shutdown branch. Only do the poll()-based version of zmq_poll (), the select()-based version will not compile at the moment.
2010-08-25REP socket layered on top of XREP socketMartin Sustrik
2010-08-25REQ socket implementation is layered on top of XREQMartin Sustrik
2010-08-25Destruction of session is delayed till both in & out pipes are closedMartin Sustrik
2010-08-25WIP: Socket migration between threads, new zmq_close() semanticsMartin Sustrik
Sockets may now be migrated between OS threads; sockets may not be used by more than one thread at any time. To migrate a socket to another thread the caller must ensure that a full memory barrier is called before using the socket from the target thread. The new zmq_close() semantics implement the behaviour discussed at: http://lists.zeromq.org/pipermail/zeromq-dev/2010-July/004244.html Specifically, zmq_close() is now deterministic and while it still returns immediately, it does not discard any data that may still be queued for sending. Further, zmq_term() will now block until all outstanding data has been sent. TODO: Many bugs have been introduced, needs testing. Further, SO_LINGER or an equivalent mechanism (possibly a configurable timeout to zmq_term()) needs to be implemented.
2010-08-25zmq_stopwatch_stop: Don't return EFAULTMartin Lucina
Function returning unsigned long int cannot return (-1)
2010-08-1146 - Devices vulnerable to invalid messagesPieter Hintjens
http://github.com/zeromq/zeromq2/issues#issue/46 Invalid messages are now discarded silently, instead of causing an assertion failure.