- 04 May, 2016 1 commit
-
-
Doron Somech authored
-
- 29 Jan, 2016 4 commits
- 28 Jan, 2016 2 commits
-
-
somdoron authored
-
Constantin Rack authored
Solution: update to 2016
-
- 19 Jan, 2016 1 commit
-
-
somdoron authored
-
- 11 Sep, 2015 1 commit
-
-
Pieter Hintjens authored
We do not use 'get' for getters. Solution: rename to zmq_msg_routing_id () for public API.
-
- 23 Jun, 2015 1 commit
-
-
Marin Atanasov Nikolov authored
-
- 14 Jun, 2015 1 commit
-
-
Jens Auer authored
The shared reference count was not shared but copied. msg_t cannot store the refcnt itsef but has to store a pointer to an externally allocated (shared) refcnter. The changes to lmsg are reverted to use content_t again. Howver, this introduces an allocation in v2_decoder when creating the message which can be avoided. When allocating the reception buffer, space is allocated for the maximum number of reference counts (8192 / max_vsm_size = 8192/64 = 128 zmq:atomic_counter objects). This increases the buffer by 128*sizeof(atomic_counter) = 128*4 = 512 bytes only. When creating a message, the refcnt member is set to the address of one of the pre-allocated atomic_counter_t objects. To do so, a new msg_t type zcmsg is introduced because msg::copy must discriminate between the message types when releasing memory.
-
- 03 Jun, 2015 1 commit
-
-
Jens Auer authored
With a msg_t size of 64 bytes, it becomes possible to embedd the content_t's members struct for large messages directly in the msg_t. This saves the dynamic allocation of content_t obejcts when using msg_t::init_data. content_t contains a zmq::atomic_counter_t object which is not a POD in C++98 and thus it cannot be used as a member of the union u. To bypass this, C++11 is used which has relaxed rules for POD and atomic_counter is a C++11-POD. An alternative would have been to make atomic_counter a classical POD by removing constructors and all private member functions, i.e. have a struct and free functions to manipulate it. A new msg_t::init function is added which decides to either to copy the data for size<64 bytes or use msg_t::init_data to do zero-copy initialization.
-
- 02 Jun, 2015 1 commit
-
-
Pieter Hintjens authored
Of course people still "can" distributed the sources under the LGPLv3. However we provide COPYING.LESSER with additional grants. Solution: specify these grants in the header of each source file.
-
- 01 Feb, 2015 1 commit
-
-
somdoron authored
-
- 22 Jan, 2015 1 commit
-
-
Pieter Hintjens authored
Solution: update for 2015 Fixes #1320
-
- 10 Jan, 2015 1 commit
-
-
Thomas Rodgers authored
Increasing it would have at least two benefits - * More messages would be 'VSM' messages, so it would reduce allocation overhead a bit. * Remove any chance of false sharing of things that are, by design, pushed by value onto a ypipe_t<msg_t> which is shared between two threads. The only downside I see is slightly increased memory consumption on memory constrained applications. - Full discussion of this rationale is part of issue #1295
-
- 13 Aug, 2014 1 commit
-
-
Martin Hurton authored
-
- 03 May, 2014 1 commit
-
-
Martin Hurton authored
We use metadata_t directly. No need for generic interface now.
-
- 30 Apr, 2014 1 commit
-
-
Martin Hurton authored
- copy and move message operations are updated to maintain proper reference count of properties object - zmq_msg_gets updated to use i_properties interface to fetch property value - setter/getter added to msg_t class
-
- 29 Apr, 2014 1 commit
-
-
Martin Hurton authored
-
- 12 Jan, 2014 1 commit
-
-
Martin Hurton authored
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.
-
- 08 Jan, 2014 1 commit
-
-
Martin Hurton authored
-
- 07 Jan, 2014 1 commit
-
-
Stefan Radomski authored
Also moved the fd field from message content to message itself
-
- 06 Jan, 2014 1 commit
-
-
Stefan Radomski authored
This patch allows client applications to retrieve the remote endpoint from a message that originated from a tcp socket
-
- 02 Jan, 2014 1 commit
-
-
Pieter Hintjens authored
-
- 04 Sep, 2013 1 commit
-
-
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
-
- 19 Aug, 2013 2 commits
-
-
Uli Köhler authored
-
Uli Köhler authored
-
- 18 Aug, 2013 1 commit
-
-
Uli Köhler authored
-
- 12 Mar, 2013 1 commit
-
-
Pieter Hintjens authored
Copyrights had become ads for Sustrik's corporate sponsors, going against the original agreement to share copyrights with the community (that agreement was: one line stating iMatix copyright + one reference to AUTHORS file). The proliferation of corporate ads is also unfair to the many individual authors. I've removed ALL corporate title from the source files so the copyright statements can now be centralized in AUTHORS and source files can be properly updated on an annual basis.
-
- 31 Jul, 2012 1 commit
-
-
Martin Hurton authored
When a peer reconnects, the router socket receives an identity message containing this peer id. When this happens, the current implementation crashes. This patch makes a router socket to silently ignore all identity messages coming from reconnected peers.
-
- 17 Feb, 2012 1 commit
-
-
Mikko Koppanen authored
-
- 16 Feb, 2012 1 commit
-
-
Pieter Hintjens authored
* Fixed use of ssize_t in zmq_msg_t class * Corrected error after merge, old reference to inner_fctname (broke build)
-
- 04 Nov, 2011 1 commit
-
-
Martin Sustrik authored
However, the "durable socket" behaviour wasn't re-added. Identities are used solely for routing in REQ/REP pattern. Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
-
- 01 Nov, 2011 2 commits
-
-
Martin Sustrik authored
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
-
Martin Sustrik authored
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
-
- 31 Oct, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
-
- 27 Oct, 2011 1 commit
-
-
Ben Gray authored
Signed-off-by: Ben Gray <ben@benjamg.com>
-
- 02 Sep, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
-
- 17 Jul, 2011 1 commit
-
-
Martin Sustrik authored
GENERIC allows to use 0MQ as a dumb networking framework. It provides user with connect/disconnect notifications. Also, each inbound message is labeled by ID of the connection it originated from. Outbound messages should be labeled by the ID of the connection to send them to. To distinguish connect/disconnect notifications from common messages, COMMAND flag was introduced. Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
-