From: Adrian von Bidder avbid...@fortytwo.ch
Date: Wed, 17 Mar 2010 22:14:49 +0100
Subject: Debian packaging for 2.0.6
Heyho!
Below the Debian packaging in 2.0.6, you may want to import it into git.
I think I'll continue to work in the hg repository I've got right now,
because I don't have the
Nelson,
We're now suffering one show stop issue of release 206:
1.) we could build the release success and okay to build our c++
program with the library
2.) we could startup our c++ program smoothly
3.) but any time server got the message from client, it crashed and
memory dump!!
On Thu, Mar 18, 2010 at 3:23 AM, Martin Sustrik sust...@250bpm.com wrote:
Hi Jeff,
I made some C# bindings a few weeks ago, but just committed it and
pushed it:
http://github.com/s450r1/zeromq2/blob/master/bindings/clr/Zmq.cs
Nice! Can you attach a licnese to the code so that it can be used
Hi Jeff,
I made some C# bindings a few weeks ago, but just committed it and
pushed it:
http://github.com/s450r1/zeromq2/blob/master/bindings/clr/Zmq.cs
Nice! Can you attach a licnese to the code so that it can be used safely?
LGPL would be preferable.
I knew I was forgetting something.
Martin,
Thanks for clarifying this. I just ran wireshark to try to understand
how all this works:
* 1 XREQ socket with HWM=LWM=2.
* 2 REP sockets that are connected that also have HWM=LWM=2.
Then I just started sending messages on the XREQ. I could see from
wireshark that the messages
Martin,
I have done some further testing with simple ZMQ_HWM on P2P sockets.
* I am using a pair of P2P sockets, both with HWM=LWM=2.
* No matter what sequence of sends/recv I do, messages are always sent
immediately (I see this on wireshark).
* I put in debug statements into pipe.cpp. I can
Hi Brian,
I have done some further testing with simple ZMQ_HWM on P2P sockets.
* I am using a pair of P2P sockets, both with HWM=LWM=2.
* No matter what sequence of sends/recv I do, messages are always sent
immediately (I see this on wireshark).
* I put in debug statements into pipe.cpp.
Martin,
Thanks for the clarification. This is quite different from how I was
thinking about it.
* Is the process lossy? Do any messages get lost when the SENDBUF/RECVBUF
fill up?
* Could we add this description to the docs?
* Can I think of the sender stopping sending messages at HWM +
Hi Adrian!
First of all, thank you for the express upload!
Below the Debian packaging in 2.0.6, you may want to import it into git.
Importing it into git (thus minimizing your diff) is a good idea. I'll look
into it soonish.
I think I'll continue to work in the hg repository I've got right
Hi
a) For my sol 10 build I do not appear to need the -D POSIX_C .
flag. (is it a GCC only thing)
b) Sunstudio 12.1 CC std::make_pair not make std::string from const char*
c) the Sun compiler CC doesnt like a variable called sun as it defines
this in a #define
Jon
diff --git
Hi,
j...@totient.co.uk said:
a) For my sol 10 build I do not appear to need the -D POSIX_C .
flag. (is it a GCC only thing)
It's not a GCC thing, it's a POSIX feature selection macro. If it doesn't
hurt I'd rather leave it in.
b) Sunstudio 12.1 CC std::make_pair not make std::string
j...@totient.co.uk said:
a) For my sol 10 build I do not appear to need the -D POSIX_C .
flag. (is it a GCC only thing)
It's not a GCC thing, it's a POSIX feature selection macro. If it doesn't
hurt I'd rather leave it in.
the configure thing went a bit loopy with it present
Here's the application that I'm using to test:
int main( int argc, char *argv[] )
{
int signum = 0;
zmq::message_t msg;
zmq::socket_t* sock1;
zmq::socket_t* sock2;
zmq::context_t ctx ( 1, 1, 0 );
sock1 = new zmq::socket_t( ctx, ZMQ_SUB );
sock1-connect(
mgi...@gmail.com said:
I'm not sure what the problem was on my machine but after fooling the network
interface into thinking that eth0 was a static IP and restarting, the C_API is
now happy to return 0 from getaddrinfo.
Modern technology. *sigh*
I would venture a guess that avahi-autoipd and
Hi Matthew,
mgi...@gmail.com said:
Here's the application that I'm using to test:
[snip]
Looks fine though I'm not sure what you're trying to achieve...
This produces:
sock1 recv: 0xfce9e8
sock2 recv: 0xfcece8
poll...
terminate called after throwing and instance of 'zmq::error_t'
I want to have all communications for my program done over 0MQ running
on a separate thread. This thread has an infinite loop calling poll on
all the sockets I want to read from, and calls different handlers for
incoming messages. The other thread does processing and stuff.
Now, one of the
I'm simply trying to get the simplest possible 'polling' example working. I
have two local PUB sockets sending a message every second, on ports 5550,
5551. The recv printout just verifies that I'm able to receive messages,
prior to then attempting to poll.
I actually exported CXXFLAGS=-ggdb3 and
17 matches
Mail list logo
