Re: [zeromq-dev] Clean shutdown of malamute client zactor in python binding?

Ah, yes, I said what I want to do but not why. The test script doesn't need a thread at all, you're correct. One of my real use cases is a web server process, where I want to have a long-lived client that is shared among requests. On 4 February 2016 at 03:04, Arnaud Loonstra

[zeromq-dev] Proposal: Add sequence number to XRAP requests

I have made a pull request to the 40/XRAP protocol to add a sequence number to the requests. Note that I have made this an incompatible change. Open to suggestions on whether it should attempt to maintain compatibility by, for example, changing the signature of the messages. I also propose

Re: [zeromq-dev] Clean shutdown of malamute client zactor in python binding?

As long as it is in Python it will be sequential anyway. In a real concurrent setup you probably want n:1 topology in between the webservers and the malamute instance and pass messages, right? Rg, Arnaud On 2016-02-04 11:37, Aaron Sokoloski wrote: > Ah, yes, I said what I want to do but not

[zeromq-dev] ZeroMQ on QNX

Dear Sir/Madam, We are interested in usage of ZeroMQ on QNX for some of our projects. Could you provide us with information about current status of ZeroMQ on QNX? In particular: 1. Possibility to use ZeroMQ on QNX Neutrino 6.5 and 6.6; 2. ZeroMQ's functional limitations on QNX;

[zeromq-dev] Should Add Windows Instructions to INSTALL or README?

Simple question. My story of why it may be helpful is below: I've been trying to build a static library on Windows, and the 4.1.4 source gave me an error that it couldn't find 'if_nametoindex', which one response suggested may be fixed in master (

[zeromq-dev] VS2013, Targets Can't Find libzmq.lib When Linking

In the zeromq-master, once I configure the VS projects and build, libzmq seems to compile and build correctly, but the other 6 projects all fail to find 'libzmq.lib'. I have tried with various configuration and architecture combinations. I'm not entirely sure what they do (test the library, I

Re: [zeromq-dev] Clean shutdown of malamute client zactor in python binding?

Of course. At the moment we're protecting access using locks, which is probably slower and more complicated than message passing but seems to be working. On 4 February 2016 at 07:49, Axel Voitier wrote: > Python makes threading sequential, yes. But it can still chops

Re: [zeromq-dev] Clean shutdown of malamute client zactor in python binding?

Python makes threading sequential, yes. But it can still chops execution of a thread in the middle of a function. Such as a function writing to a shared buffer to be flushed on a zmq socket later. That is how you can end up with messages mixed up if two threads use the same function and/or write

Re: [zeromq-dev] Clean shutdown of malamute client zactor in python binding?

Maybe Tornado would work for what you're trying to do: http://www.tornadoweb.org/en/stable/ It has an asynchronous web server that can be integrated with 0MQ. On 2/4/16 7:41 AM, Aaron Sokoloski wrote: > On 4 February 2016 at 05:45, Arnaud Loonstra

Re: [zeromq-dev] Clean shutdown of malamute client zactor in python binding?

Heh, I'm dealing with a pretty big legacy code base, which at the moment uses cherrypy :( I can only tackle one bit at a time. Thanks for the tip though. On 4 February 2016 at 07:49, Colin Ingarfield wrote: > Maybe Tornado would work for what you're trying to do: >

[zeromq-dev] Node.js over Zyre

Hi all, I've started on a Zyre binding for Node.js. It's an experiment that will feed into a proper target for zproject. The code is here: https://github.com/zeromq/zyre/pull/412 (on zyre master as soon as it's merged). Pull requests welcome as usual. -Pieter

Re: [zeromq-dev] Node.js over Zyre

On 2016-02-04 15:16, Pieter Hintjens wrote: > Hi all, > > I've started on a Zyre binding for Node.js. It's an experiment that > will feed into a proper target for zproject. > > The code is here: https://github.com/zeromq/zyre/pull/412 > > (on zyre master as soon as it's merged). > > Pull requests

[zeromq-dev] zmq4 and zmq3

Hi, If I have zmq4 (PUSH) application will it work connecting to zmq3 (PULL)? I did try to the online documentation… /Thomas Have +45 50600777 [http://imageshack.com/a/img911/6069/V1ypg0.png] ___ zeromq-dev mailing list

Re: [zeromq-dev] Clean shutdown of malamute client zactor in python binding?

I'm not sure if I can follow you but why do you want to use malamute in separate thread? In python this has no benefits. The approach you have is correct but you don't need a thread for that if I'm not mistaken. I would avoid any threading if you can. Rg, Arnaud On 2016-02-03 18:57, Pieter

Re: [zeromq-dev] zmq4 and zmq3

Yes. ZeroMQ is backwards compatible to version 2.x On Thu, Feb 4, 2016 at 5:11 PM, Thomas Have wrote: > Hi, > > If I have zmq4 (PUSH) application will it work connecting to zmq3 (PULL)? > > I did try to the online documentation… > > */Thomas Have* > +45 50600777 >

Re: [zeromq-dev] zmq prebuilt for node

Neat, that's what we want. On Thu, Feb 4, 2016 at 5:12 PM, Kyle Kelley wrote: >> How does prebuild differ from node-pre-gyp? > > prebuild lets you upload to GitHub for releases whereas node-pre-gyp expects > you to push releases to S3. It appears that the builds from prebuild

Re: [zeromq-dev] Clean shutdown of malamute client zactor in python binding?

On 4 February 2016 at 05:45, Arnaud Loonstra wrote: > As long as it is in Python it will be sequential anyway. In a real > concurrent setup you probably want n:1 topology in between the > webservers and the malamute instance and pass messages, right? > Well, yes, but this is

Re: [zeromq-dev] Node.js over Zyre

Yes, the more merges the better... :-) I wanted this to go onto master so others could play with it. On Thu, Feb 4, 2016 at 4:36 PM, Arnaud Loonstra wrote: > On 2016-02-04 15:16, Pieter Hintjens wrote: >> Hi all, >> >> I've started on a Zyre binding for Node.js. It's an

Re: [zeromq-dev] zmq prebuilt for node

> How does prebuild differ from node-pre-gyp? prebuild lets you upload to GitHub for releases whereas node-pre-gyp expects you to push releases to S3. It appears that the builds from prebuild are compatible with node-pre-gyp ( https://github.com/mafintosh/prebuild#building). I'm still learning

Re: [zeromq-dev] zmq prebuilt for node

I've two questions: - How does prebuild differ from node-pre-gyp? - How do you make an "official" package so that npm knows where to find it? I'd probably aim at making this the official zmq package eventually, and bring it into the zeromq organization. On Thu, Feb 4, 2016 at 8:12 AM, Kyle