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 t
In your private byte[] getByte(...), I see that you create and destroy
our context each time it's called. I would try creating only one
context for your client process and see if that helps your
reliability.
http://zguide.zeromq.org/page:all#Getting-the-Context-Right
-Trev
On Mon, Mar 11, 2013 a
> So aside, from a version number increase, and few changed comments, there
> doesn't seem be any real software upgrade, i.e. no src files modified, am I
> wrong?
>
There should have been a few files changed:. This is the diff from the
v2.1.2 tag with master:
https://github.com/zeromq/jzmq/compar
Great!
I didn't noticed PR 338.. So it's really fully fixed in master.
2013/3/11 MinRK
> To further clarify, there are two cases:
>
> 1. no sigint handler registered - ^C absolutely should result in
> KeyboardInterrupt. This behavior is intended, and has not changed since
> 2.1.9.
> 2. sigint
Hello Min,
Thank you a lot for update.
Please find attached out test case code excerpt attached.
Your insight would be highly appreciated.
Thanks,
Erwin
AT&T, Senior Software Architect
public class PublisherMeasured extends MeasuredMasterPeer {
static String PUB_PORT = ":5559";
st
To further clarify, there are two cases:
1. no sigint handler registered - ^C absolutely should result in
KeyboardInterrupt. This behavior is intended, and has not changed since
2.1.9.
2. sigint handler registered - in this case, KeyboardInterrupt should *not*
be raised, and the regular ZMQError(
Hi All,
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.
-Pieter
__
On Mar 11, 2013, at 13:13, Jonathan Kamens wrote:
> Greetings,
>
> With PyZMQ versions prior to 13.0.0, we were running into problems with
> certain PyZMQ calls getting interrupted by restartable signals (e.g.,
> SIGALRM) used by our application. We fixed this problem like this:
>
great...that is what I was trying to confirm :-) Thanks Pieter!
" So zmq has to somehow copy the VSM before the message variable goes out
of scope. Just want to confirm that zmq does that."
On Mon, Mar 11, 2013 at 2:13 AM, Pieter Hintjens wrote:
> Very small messages (under 30 bytes at present)
Greetings,
With PyZMQ versions prior to 13.0.0, we were running into problems with
certain PyZMQ calls getting interrupted by restartable signals (e.g.,
SIGALRM) used by our application. We fixed this problem like this:
while True:
try:
On 11 March 2013 12:09, Emmanuel TAUREL wrote:
> scons -f SConstruct.RHEL4
>
You probably want,
scons -f SConstruct.RHEL4 BUILD=RELEASE WITH_EXAMPLES=false
WITH_HTTP=false WITH_SNMP=false WITH_HISTOGRAMS=false
Comment out the lines in the SConstruct file to avoid the errors:
if not conf.Che
Hi Steve,
I have downloaded libpgm 5.2.122 and scons 2.2
I have the following error when I try to build pgm:
scons -f SConstruct.RHEL4
scons: Reading SConscript files ...
scons: warning: The Options class is deprecated; use the Variables class
instead.
File
"/mntdirect/_users/taurel/src/libpg
On 11 March 2013 09:44, Emmanuel TAUREL wrote:
> I am trying to compile ZMQ 3.2.2 using pgm (5.1.118) on one relatively
> old Linux box: Red Hat release 4. The compiler release is gcc 3.4.6.
>
Can you try building the *libpgm *library independently, maybe trying
version 5.2.122.
I recall proble
Hello all,
I am trying to compile ZMQ 3.2.2 using pgm (5.1.118) on one relatively
old Linux box: Red Hat release 4. The compiler release is gcc 3.4.6.
The compilation failed when compiling pgm with the following message:
time.c:451:4: #error "gettimeofday() or ftime() required to calculate
cou
I've just downloaded a new ZIP from the GIT repository, and found out that the
pom.xml file says 2.1.3-snapshot. Used diff to compare files with the prior
version I had and the output was the following:
diff jzmq-master "jzmq-master 2"
Only in jzmq-master: .DS_Store
diff jzmq-master/INSTALL jzmq
Very small messages (under 30 bytes at present) are copied around
rather than referenced.
-Pieter
On Mon, Mar 11, 2013 at 8:04 AM, Mohit Jaggi wrote:
> Hmm...but messages are not sent in the context(I don't mean zmq context
> here) of the calling thread, right? So, how can one use stack variable
Hmm...but messages are not sent in the context(I don't mean zmq context
here) of the calling thread, right? So, how can one use stack variable for
message object?
On Sun, Mar 10, 2013 at 11:08 PM, Pieter Hintjens wrote:
> On Mon, Mar 11, 2013 at 12:39 AM, Mohit Jaggi
> wrote:
>
> > I understan
17 matches
Mail list logo
