On 2015-02-06 10:11, Joe McIlvain wrote:
Integer routing ids sounds nice to me, quite honestly.
Just a small comment on this:
I've used fixed-sized integer IDs in nanomsg and, in retrospect, I think
it was an error.
In particular, think of UDP or any other unconnected protocol as a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/08/14 14:04, Pieter Hintjens wrote:
On Thu, Aug 14, 2014 at 12:22 PM, Michi Henning mi...@triodia.com
wrote:
On that note: Why is zmq using void * instead of declaring
abstract types?
Horrid C API design by individuals who felt C++ was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31/12/13 09:59, Wojtek Sliwinski wrote:
For many industrial control systems, UDP is the solution when we
talk about: - high frequency (50Hz) messaging - scalability:
minimal load use of resources on publisher's side - some messages
may be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31/12/13 11:21, Arnaud Loonstra wrote:
Don't you mean SCTP? DCCP also does not do ordered delivery to my
knowledge.
Oops, haven't looked at DCCP specs for a long time...
Martin
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/11/13 02:49, Winston Smith wrote:
Is it possible to trunk or multiplex each of these patterns into
a single channel?
Think of what would happen if there was pushback exercised on one of
the channels. It would block *all* the channels. With
On 2013-10-01 16:09, gonzalo diethelm wrote:
OK, this is what I am thinking, in a very rough first cut, of how
ZMQ_MONITOR should work. Some notes follow. Comments are welcome.
What about the fact that monitoring events are queued and thus delivered
with a delay? By the time you get CONNECTED
Hi Gonzalo,
1.Is there an architecture diagram / document explaining how everything
fits together?
You can find a high level overview here:
http://www.aosabook.org/en/zeromq.html
I've also written a bit more concrete document here:
http://www.zeromq.org/whitepapers:architecture
However,
Hi Erwin,
No it is not possible to detect the failure of the peer. The problem is
inherently semi-decidable, i.e. you can make sure that peer is alive (if
it responds), but there's no way to distinguish a peer failure from a
slow/dead network.
Thus the only thing you can do is a handshake
On 2013-05-24 11:20, Pieter Hintjens wrote:
Hi all,
I've updated the Wikipedia page, which was out of date.
https://en.wikipedia.org/wiki/%C3%98MQ
Sustrik, you might want to add a reference to Nano in the History
section; I didn't do that but it should probably be there.
Thanks for
IIRC the problem was that some users had problems with firewalls
blocking TCP connections on top of loopback interface. Fixed port number
allows you to configure the firewall as to allow this kind of internal
connections.
Martin
On 2013-05-09 16:08, KIU Shueng Chuan wrote:
Browsing through
Hi Pieter,
We've been working on a proof of concept for distributed security for
0MQ, based on CurveCP [http://curvecp.org/].
Here's a first blog posting on the topic: http://hintjens.com/blog:34.
The goal is to build this into a reusable security layer for 0MQ apps.
Nice! I've been
On 21/02/13 10:31, Bjorn Reese wrote:
PS: What is the rationale for creating the Zyre discovery protocol
rather than reusing one of the existing discovery protocols (ZeroConf,
SSDP, SLP, etc.) ?
I would second that. Discovery is a complex topic and lot of RD was
already done in the area.
On 19/02/13 12:08, Martin Lucina wrote:
sust...@250bpm.com said:
On 23/01/13 09:44, DEBROUX Lionel wrote:
http://lwn.net/Articles/504722/
Sadly, while it has some clear use cases, AF_BUS is not part of the
mainline kernel, it remains an out-of-tree patch...
It was added to a patched
On 23/01/13 09:44, DEBROUX Lionel wrote:
http://lwn.net/Articles/504722/
Sadly, while it has some clear use cases, AF_BUS is not part of the
mainline kernel, it remains an out-of-tree patch...
It was added to a patched third-party 3.4.x kernel yesterday, as part
of the LTSI (used only by a
On 18/01/13 09:10, Pieter Hintjens wrote:
On Fri, Jan 18, 2013 at 2:00 AM, KIU Shueng Chuannixch...@gmail.com wrote:
I think there was some effort from 2.2 to 3.2 to give ZMQ a more similar
interface to regular sockets?
e.g. Changing the send function to return the number bytes sent on
Hi Sebastian,
I am working on one here: https://github.com/250bpm/nanomsg
It's in early stage of development though, so if you are looking for
something fully stable, it's not what you want.
Martin
On 21/12/12 19:29, Sebastian Freundt wrote:
Hi,
I was wondering if there's any known pure C
On 03/12/12 23:19, Justin Karneges wrote:
Slightly OT, but I wonder if RATE might be a useful feature to allow for all
PUB sockets (and maybe just all sockets), rather than restricted to pgm only.
It seems to me that you want to use RATE when you need to slow down sending
but can't depend on
On 08/10/12 12:34, Michael Haberler wrote:
My first pull request ever is out of the gates. Hope I got it right.
Kudos!
Martin
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
On 28/09/12 02:09, MinRK wrote:
I'm not sure where all of the FD requests are, but one is inbound
connections. Is it possible/sensible to simply reject new connections
if FD allocation fails?
If anyone more familiar with the core can enumerate all of the FD
allocations, then perhaps we can
On 28/08/12 13:38, Pieter Hintjens wrote:
On Tue, Aug 28, 2012 at 5:25 PM, Simon Dawsonspdaw...@gmail.com wrote:
However, in the COPYING.LESSER file, it is stated that Parts of the
software are licensed under the MIT (X11) license. I can find no
evidence of any such parts; do such parts
Hi all,
The Architecture of Open Source Applications book, volume II, is
finally out:
http://www.aosabook.org/en/index.html#vol2
Aside of other content it contains my article on architecture of
Crossroads/ZeroMQ:
http://www.aosabook.org/en/zeromq.html
Enjoy!
Martin
On 18/04/12 00:40, Paul Colomiets wrote:
Unlike old devices, paperjam provides standalone process with multiple
devices in single process (and with YAML'y config).
Future plans are modest: implement handling of various socket options,
add some statistics and maybe implement zeromq3 support.
, and also everyone who we have discussed the fork with over the
last couple of months for their help and advice.
Regards,
Martin Sustrik
Martin Lucina
--
Crossroads I/O Release Notes
This file
On 08/02/12 19:15, Gary Wright wrote:
On Feb 8, 2012, at 10:25 AM, john skaller wrote:
Interesting things is .. all this fuss about thread-safety .. and actually,
these atomic ops are used in the msg_t functions .. the ones least
likely to span thread boundaries :)
Perhaps they traverse
On 02/07/2012 05:41 PM, Nadav Samet wrote:
I'm not sure I follow, what's evil about callbacks? In particular, I am
working on an RPC library on top of ZeroMQ. It spawns n threads, and
whenever a request arrives it runs a user-supplied function (i.e.
callback) on one of these threads. Are
On 07/02/12 14:52, john skaller wrote:
If you have only stateless processing,
meaning every request is entirely independent, a callback is fine.
That's a great rule of thumb! It deserves being documented somewhere.
Martin
___
zeromq-dev mailing list
Hi Staffan,
I'm taking a look at fixing https://zeromq.jira.com/browse/LIBZMQ-299,
and I'm not quite sure how to tackle it.
There are two problems concerning HWMs and (X)SUB as I see it:
1. Subscriptions are silently dropped if the SNDHWM is reached. I don't
know if that's the intended
Hi John,
If you initialise the message empty, zmq_recvmsg will allocate
exactly the right amount of space for you. This is ideal.
But there's no way to get the buffer out of the msg, you have
to copy it. This is wastes a memcpy, and wastes storage temporarily.
You have to copy it because
Hi Nadav,
I like the concept of having thread-safe sockets, but it seems that this
implementation does not really deliver what a user would expect from a
thread-safe socket. For instance, if two threads try to
receive simultaneously from the same socket, each of them might obtain
different
On 06/02/12 22:08, Gary Wright wrote:
What makes the problem bad is the fact that there may be arbitrary
interval between sending/receiving 1st and 2nd part of the message.
During that time the socket has to be locked which in turn means that
all other threads accessing it will be blocked for
On 06/02/12 22:38, Nadav Samet wrote:
What makes the problem bad is the fact that there may be arbitrary
interval between sending/receiving 1st and 2nd part of the message.
During that time the socket has to be locked which in turn means
that all other threads accessing it
On 02/07/2012 09:57 AM, Chuck Remes wrote:
While watching this thread, I can't help but think that you wish 0mq
was a *much different* library than it is. I'm hoping that sustrik
stays engaged with it at some level to indicate how much is feasible
for his long-term vision (getting 0mq into
On 02/07/2012 10:56 AM, john skaller wrote:
On 07/02/2012, at 12:16 PM, Martin Sustrik wrote:
5. That being said, using single socket from multiple threads is not a
good design decision. It breaks the model of threads viewed as
stand-alone state machines communicating with the outside world
On 03/02/12 18:37, AJ Lewis wrote:
On Fri, Feb 03, 2012 at 05:16:06PM +, Christian Martinez wrote:
First, I have to make a disclaimer that everything I'm about to say is
my opinion only and does not reflect any official MSFT position.
Heh - I guess I should put that disclaimer on my
Message-Id:20111220091654.05261dc03816046900f83...@lucina.net
If, and only if, both Pieter Hintjens and Martin Sustrik give their consent
to making these conversations public, in their entire and unredacted form,
then I also give my consent to making these conversations public, in their
entire
On 04/02/12 02:30, john skaller wrote:
I have just added a new section to the style guide banning the calling
of public functions by public functions. Public functions are reserved
for the public.
Good idea. +1
Martin
___
zeromq-dev mailing list
On 04/02/12 14:24, Martin Lucina wrote:
Do you trust me to take the complete text of these emails and, for the
avoidance of doubt, for each each email include the following headers:
Sure. Np.
Martin
___
zeromq-dev mailing list
Hi Matteo,
we just switched our PUB/SUB architecture on 0MQ from TCP to EPGM to
reduce traffic and get over the need for a central repeater to have
multiple publisher/multiple subscribers.
I tcpdump'ed the traffic to see what was going on, but I can only see
repeated multicast messages from
On 03/02/12 11:40, Pieter Hintjens wrote:
I'd suggested this ages ago for the core API since it is a systematic
cause for confusion for new users. You create a SUB socket and connect
it, and it does nothing. Martin's argument was based iirc on
implementation aspects. Since all subscriptions
On 02/02/12 11:52, john skaller wrote:
Recall Mashal MacLuhan: The medium is the message.
Heh. Haven't expected to meet this guy here.
I suggest
such term should research existing POSIX terminology.
+1
As a side comment, the confusion stems from the fact that 0MQ protocol
is a mix of two
On 02/02/2012 10:05 PM, Chuck Remes wrote:
Lastly, I think it's time to trot out an old blog post that Martin Sustrik
wrote on this topic.
http://www.zeromq.org/blog:multithreading-magic
To give the respect where it belongs, it was Pieter who wrote the
article. I've only supplied
On 02/02/2012 11:23 PM, john skaller wrote:
It's likely applications such as a webserver will have a set of waiting
fibres (one per connection or more), and they'll be farmed out to
an arbitrary p-thread allocated from a pool. In that case, how can
the client possibly obey the Rule since they
On 01/28/2012 10:41 AM, Martin Lucina wrote:
4) The patch does not conform to http://www.zeromq.org/docs:style.
+1
If the
code went verbatim into its own file this is fine, but again, not in
blob.hpp.
foreign subdirectory would be a good place for this.
Martin
Hi,
* SUB sockets default to SUBSCRIBE() instead of None
This becomes a problem with 3.0 and subscription forwarding. The problem
occurs when you don't want to subscribe to all messages. You open a
socket and unsubscribe from . However, between the two operations you
can be overloaded by
On 30/01/12 10:49, Staffan Gimåker wrote:
2. https://github.com/zeromq/libzmq/pull/227
Reduce memory usage of mtrie. Instead of keeping a std::set around for
only mtrie nodes we only allocate it when needed. Worst case this
increase memory usage by sizeof(void*) bytes per node, but typically
Hi Michael,
Note that id3lib_strings.h is GPL-licensed. It cannot be turned into LGPL.
Martin
On 27/01/12 23:17, Michael Fox wrote:
I submitted a pull request on github, to fix build issues on old Linux
(Redhat circa 2002, 2.4 kernel, 3.2 gcc).
But it looks like it may also be necessary to
On 28/01/12 01:03, Mikko Koppanen wrote:
http://id3lib.cvs.sourceforge.net/viewvc/id3lib/id3lib-devel/include/id3/id3lib_strings.h?revision=1.8view=markup
it looks like id3lib_strings.h is under LGPL (not sure if this is the
file in question).
I've seen a different version with GPL license.
On 26/01/12 18:34, Rick Flower wrote:
Any issues you can see? I've already swapped the order in
my local version of the code and rebuilt everything and it
works great!
As already mentioned by John, the problem is fixed in 3.1.
As for 2.1 the patch breaks ABI (although it leaves API alone)
On 26/01/12 15:57, Martin Lucina wrote:
zmq_bind(foo, tcp://:*);// tcp://*:* if you want INADDR_ANY
char endpoint [ZMQ_ENDPOINT_MAX];
zmq_getsockopt(foo, ZMQ_GET_ENDPOINT, endpoint, sizeof endpoint);
= endpoint is filled as tcp://:12345.
Note that out of the two wildcards, only
On 26/01/12 00:34, Yi Ding wrote:
Basically right now we have to call zmq_recv repeatedly until we get a
EAGAIN, otherwise the edge-triggered file descriptor won't reset. The
problem is that calling zmq_recv on a rep or req socket can also return
a EFSM, which will trigger an exception in
On 01/25/2012 04:49 PM, Staffan Gimåker wrote:
I couldn't really figure out a way to unify the pub and sub-side of the
filtering, no. Maybe if more templates/meta programming-tricks are ok I
can come up with something. The pub and sub side do things just
differently enough that it's tricky to
Hi Boris,
PS: On bind it fails because of the following line (tcp_listener.cpp:70):
rc = setsockopt (s, SOL_SOCKET, SO_EXCLUSIVEADDRUSE,
(const char*)flag, sizeof (int));
It seems to me that sockets on WM does not support this option.
You may try SO_REUSEADDR instad. It's
Hi Yi,
However, if we use REQ/REP in conjunction with ZMQ_FD, as we currently
do in our code and nzmqt (I'm sure it's also used in other bindings)
EFSM is basically unavoidable as triggering a EFSM is required if we
want to reset the receive state for the edge-triggering.
Can you explain the
On 01/26/2012 11:13 AM, Michael Craig wrote:
In a bunch of the marketing copy, ZeroMQ claims to handle N-to-N
topologies. Is this actually true? It would seem not, since one side of
a Push/Pull or Pub/Sub topology has to bind (which only one node can
do). The closest I can figure out is an
Hi,
I think that posting of 0MQ-related jobs on the ML is OK. If any spam
appears, additional measures can be taken.
Btw, I also have zeromq group on linked-in that's not used for anything
at the moment. If people believe linking their linked-in CVs to the
group would be useful, I am happy to
On 24/01/12 09:32, Staffan Gimåker wrote:
Here's an initial go at this if anyone wants to have a look:
https://github.com/gimaker/libzmq/tree/exact-matching
https://github.com/gimaker/libzmq/tree/exact-matchingIt probably needs
a bit more polish and documentation, but it'd be nice to get
Hi Joegen,
PUB socket sends every message to *every* subscriber. Thus they should
arrive at the destinations at approximately the same time.
Exact time of course depends on network latency between publisher and
individual subscribers.
Martin
On 01/25/2012 10:41 AM, Joegen Baclor wrote:
Just
On 01/25/2012 11:30 AM, Michel Pelletier wrote:
If I follow what you're asking, you want the numbers in your first
email to have a more even distribution than what they have now, where
no one subscriber gets the message first, so to speak. I'm not sure
it makes sense for 0mq to try to make
On 01/25/2012 05:26 AM, Chuck Remes wrote:
I see this ETIMEDOUT error quite a bit when my machine is under a
little bit of load so I agree that it's probably some OSX kernel
resource running out/low. (OSX is *not* a good choice for server
workloads.)
Do you have any specific suggestions on
On 01/25/2012 03:22 AM, Rick Flower wrote:
I ran
across, again, the paragraph in the guide talking about zero-copy and
want to
know if I omit the malloc/memcpy stuff if I'm going to get into trouble
since
the buffer may not be actually send (but would be queued) prior to the
message
Btw, have anyone created a ticket for this problem in the bugtracker?
Martin
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Hi Staffan,
Here's an initial go at this if anyone wants to have a look:
https://github.com/gimaker/libzmq/tree/exact-matching
https://github.com/gimaker/libzmq/tree/exact-matchingIt probably needs
a bit more polish and documentation, but it'd be nice to get some
feedback if it's on the
On 23/01/12 10:56, Sergey Matveychuk wrote:
But I cant' do it with ZMQ_SUB. Adding a control connection is
undesirable. It'll increase open connections on server twice.
What's the actual problem? Limited number of port numbers?
Martin
___
zeromq-dev
On 23/01/12 19:08, Marcin wrote:
You may want to set the lingering period to 0.
Good point.
Even then zmq_close() isn't synchronous, but is should close the FDs
very quickly (couple of microseconds).
Martin
___
zeromq-dev mailing list
On 23/01/12 20:02, Ivan Pechorin wrote:
Some VPN boxes are configured to close idle sessions after some
timeout. Some firewalls are configured to drop idle connections
(idle connection here means no traffic passes through it). For
instance, if I remember correctly, in popular Cisco ASA
On 23/01/12 18:06, Sergey Matveychuk wrote:
Well, may be it'd better to set it via zmq_setsockopt()?
Yes. I believe so.
Martin
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Hi AJ,
I too hope the LABEL work will be revisited. It seemed to me that it
was tied up with a whole bunch of other incompatible changes (to the 2.1
codebase) and got dropped when everything else did. I didn't see many
(any?) complaints about that part on the list.
I'm hoping it gets
On 24/01/12 00:56, Michael Craig wrote:
A helpful denizen of IRC pointed me to the ZeroMQ Jira, where I filed an
issue:
https://zeromq.jira.com/browse/LIBZMQ-317
jira.com seems to be down at the moment. I'll have a look later on.
Martin
___
On 24/01/12 01:22, Chuck Remes wrote:
A DEALER socket is a synonym for XREQ and a ROUTER socket is a
synonym for XREP. The REQ REP sockets are built on top of those
other types. When sending data from a REQ to a ROUTER socket, for
example, you will see that the ROUTER socket receives the
On 24/01/12 02:08, Chuck Remes wrote:
Sure, I get that. But if you ignore the convention (null delimiter)
then you can't interoperate with REQ or REP sockets. Generally the
user may want to do so in the future, so by not conforming to that
message protocol with the null delimiter they are
On 22/01/12 11:39, Rob Fowler wrote:
Note that zmq_close() is never blocking.
Ah, ok. Thanks.
If I use python and zmq close(linger=False) it will block
Hm. That must be some pyzmq-specific behaviour.
Martin
___
zeromq-dev mailing list
Chuck,
This may be a question for FAQ.
What do you think?
Martin
On 22/01/12 17:30, Michael Craig wrote:
Thanks, Pieter. Problem solved.
Mike Craig
On Sun, Jan 22, 2012 at 11:11 AM, Pieter Hintjens p...@imatix.com
mailto:p...@imatix.com wrote:
Read
Hi all,
I believe this discussion misses what I wanted to say.
There are many issues mixed here:
1. Should 0MQ provide internal message parts?
2. Should 0MQ provide application-level message parts?
3. Expose the functionality as gather-scatter arrays?
4. Should the 0MQ-related parts of the
On 22/01/12 17:02, john skaller wrote:
YMMV .. but in my plan, moving sockets across thread boundaries
is mandatory .. in fact the whole async/IO paradigm is based on it.
Yes. Many bindings do that. For example when when passing a socket to
the garbage collector.
It's an functionality for
Hi Andrew,
i am currently seeing the following scenario:
one process opens a PUSH socket on an ipc address /x/y
several processes open a PULL socket on that same /x/y
traffc flows as expected for 24-48 hrs.
then traffic stops.
the sending process is stalled in send, and all the reading
On 22/01/12 13:02, Sergey Matveychuk wrote:
I think the patch will resolve my problem.
Are you sure about that?
First, keepalives are meant for the situation where the network
connectivity between peers is broken (cable pulled out from the socket,
switch turned off etc.) Is that your use
Hi Victor,
IMHO, there are some design should be changed.
1. Add an option to determine whether to buffer data on connecting sockets
I'm not sure the reason why connecting sockets buffer data, but I think
it's for to sync easily. To make the behavior not so surprising, it's
better to
On 23/01/12 02:49, Martin Lucina wrote:
I did not follow the LABEL work, but IIUC the problem was you tried to
satisfy point 4) above by breaking point 2), right?
Nope. The functionality was still there. The idea was to use one flag
for 0MQ-level message parts (ZMQ_LABEL) and another flag for
On 21/01/12 08:51, john skaller wrote:
Just curious .. why does 0MQ use select on Windows?
Instead of IO completion ports?
Many have tried to patch this and many have failed :)
It's a reoccuring problem that has an impact of quite o lot of features.
For example NamedPipes cannot be used for
On 21/01/12 14:38, john skaller wrote:
Why?
I can't see what it does. Since there's no transmission until all the parts
are collated
and no reception until all the parts are collated .. what's wrong with the
client
doing that and just sending one big message?
The original reason for
On 21/01/12 23:34, john skaller wrote:
Which ops in 0MQ can block?
I know these can block:
send/recv/send_msg/recv_msg
close
term
These are blocking: send, sendmsg, recv, recvmsg, poll, term.
Note that zmq_close() is never blocking.
can anything else block? Most of the other ops would
On 21/01/12 10:08, john skaller wrote:
Unfortunately, whilst I can run Vista on my Mac, I don't have any development
tools.
(And I'm not going to download them using wireless internet which is all I
can use
at the moment;)
If anyone wants to look at this problem, Felix has support for
Hi Sergey,
I have a ZMQ_PUB server (FreeBSD) and many (~300) ZMQ_SUB clients
(FreeBSD and Linux). Sometimes I see a wierd problem on some Linux
clients. netstat -a on server shows no connection with a client, but on
the client netstat -a shows an established connection:
Strange. That should
On 19/01/12 17:05, john skaller wrote:
This is seriously bugged. You may not use the name DLL_EXPORT.
You must use a command line macro name specific to the library!
For example ZMQ_DLL_EXPORT.
You mean that if zmq.h is included in a header file of another library
that happens to define
On 20/01/12 07:58, Rick Nellie Flower wrote:
Martin.. Thanks for the reply.. So, to get this working with inproc, do I need
separate context() or ?? In reading the guide I thought I wanted a single
context shared among all threads in the process? Sorry for being dense..
Oops. I've misread
Hi Rick,
Hi all.. I'm new to 0MQ -- only found it this morning. I'm trying to set it
up
initially to have N threads (probably ~10) logging messages to a central
but separate thread that will receive the packets and log them to a file..
So, I found a sample pthread based sample and
. The lead developer (Martin
Sustrik) is also more of a UNIX guy than a Windows guy so, unless
there is some strong incentive for him to work on it, I think this
contribution will have to come from a community member.
I've checked the mailing list. There have been a lot of discussion about
the topic
On 18/01/12 22:07, Pieter Hintjens wrote:
ZMQ_PAIR sockets don't really fit in to the zeromq philosophy. Including
them at all was probably a mistake.
I strongly disagree, finding them perfect for a quite common use case :-)
Both of the above are true.
0mq is mainly about communication
On 01/19/2012 09:36 AM, john skaller wrote:
On 19/01/2012, at 3:57 AM, Chuck Remes wrote:
This would provide some room to grow if the library were to ever get a more
complex matching mechanism like regular expressions.
#define ZMQ_SUBSCRIBE_REGEX_MATCHint
No. The way you do this is with
Hi Andrew,
as for regex, be careful. regex performance is NOT wire speed EXCEPT
for the case of substring and in many case, multiple substrings
(the unix fgrep case). plus, relatively few folk are adept with complex
regex expressions.
Ack.
on the other hand, i don't get this use case.
can
/
Martin
On 01/19/2012 11:34 AM, John D. Mitchell wrote:
On Jan 18, 2012, at 18:25 , Martin Sustrik wrote:
[...]
as for regex, be careful. regex performance is NOT wire speed EXCEPT
for the case of substring and in many case, multiple substrings
(the unix fgrep case). plus, relatively few folk
Hi John,
May I ask what the plans are for the upgrade to 3.1 of the huge number of
examples in different languages in the excellent Guide?
I would consider adding Felix to the set of languages, however I do not
wish to support version 2.x.
I guess adding new examples shouldn't be a
On 01/16/2012 04:35 AM, john skaller wrote:
Actually I might point to the thread affinity socket option type uint64_t as
an issue here.
64 threads is not many by todays standards. Heck, cheap desktops have 4 cores
in them
already, Sun has made boxes with 64 CPU's for some time..
Good
From 962077fdbec43623c8101cec839e075ed76e1a9e Mon Sep 17 00:00:00 2001
From: Martin Sustrik sust...@250bpm.com
Date: Mon, 16 Jan 2012 17:13:58 +0900
Subject: [PATCH] Documentation of zmq_getmsgopt improved
Signed-off-by: Martin Sustrik sust...@250bpm.com
---
doc/zmq_getmsgopt.txt |2 ++
1
On 01/15/2012 03:29 PM, john skaller wrote:
zmq_getmsgopt(3) ZMQ_MORE
The type is not documented. The example shows it is an int.
Thanks for spotting this. I've sent the patch to the list.
Martin
___
zeromq-dev mailing list
On 01/15/2012 05:53 PM, Marten Feldtmann wrote:
I had asked the same question some days agon on this list, while working
on a VASmalltalk binding for this library.
It should be made clearer in the documentation, that one may reuse the
structure after the application thread has closed it.
On 15/01/12 03:33, john skaller wrote:
Note also: your argument only applies to C programmers.
How many bindings are there? (I'm just adding one more .. )
You mean like wrapping libzmq in such a way that the wrapper converts
errnos into return codes? That seems doable.
Btw, Linux kernel
On 15/01/12 12:10, john skaller wrote:
Who owns the binary data blobs using set_sockopts? And get_socopts while I'm
asking.
For identity, subscribe, unsubscribe?
I presume the caller owns them for all the others, so the function must
copy the int, uint64 etc. I assume set_sockopts copies
Hi Michael,
The binding you are referring to was written for 0MQ/0.x version, so
it's completely out of date today.
What you would have to do is either take it and heavily modify it to
suit current 0MQ API or simply create a new binding so that others can
sing you praise in the future :)
Hi Pasi,
I tried to compile zqm as a static library but it is just too much
work with every version. I was able to do it with older VisualStudio,
but with VS2010 and zmq 3.1.1 I just can't get it to work any more.
What's the error you are getting?
a) In OSX 10.7 Xcode 4.2 it seems that
1 - 100 of 2285 matches
Mail list logo
