It certainly will, but using JeroMQ is not a choice made typically for
performance reasons in the first place, right?
On Sep 10, 2014, at 10:55 AM, 曾纪川 zengjich...@outlook.com wrote:
Bernard, thanks for your answer. But I wonder that using tcp or ipc may
affect the transfer rate.
Best
that it
doesn't support like inproc, pgm and currently security. It's far
simpler to get up and running.
On Wed, Sep 10, 2014 at 6:39 PM, Stephen Riesenberg
stephen.riesenb...@gmail.com wrote:
It certainly will, but using JeroMQ is not a choice made typically for
performance reasons in the first
Sorry to reply to this late, but did you resolve your issue? I noticed in your
code snippet, you are using two different instances of ZMQ.Context, one in your
Router/Dealer queue, a different one in your Worker. I believe you would need
to use the same context in order for inproc to work. That
Sara,
How far have you gotten in your effort? Do you have an example class? What
issues did you run into? What requirements do you have for your API? Is it
files, or just data you are sending back and forth between these two
environments?
Sorry for so many questions, but I bet with a few details
Mario,
Have you had any additional thoughts on this recently? I hate to drag up an
old-ish thread, but this one seems like a good recurring conversation to
have. I wish I had been paying attention when you introduced it, but I was
not. :(
You mentioned the jzmq-api project, and I wanted to
ra/Applications/zeromq/jzmq/jzmq-jni/src/main/c++/zmq.jar
>>> -Djava.library.path=/usr/local/lib hwClient
>>>
>>> The Java program that I have built that I am trying to implement ZeroMQ
>>> with I have built within Eclipse. So I am not really used to working with
&
do I implement the following command in Eclipse?
> -Djava.library.path=/usr/local/lib hwClient
>
> Thank you all. I appreciate your help.
>
> Sincerely,
> Sara
>
>
> On Wed, Apr 27, 2016 at 9:35 PM, Stephen Riesenberg <
> stephen.riesenb...@gmail.com> wrote:
>
>
Francesco,
Have you read the ZeroMQ guide? Seems like a perfect fit. You are basically
building a single publisher that funnels messages through like a broker,
except the broker is local to the threads emitting messages. I've used this
pattern in the past. You can then treat that broker as a
, Francesco <francesco.monto...@gmail.com>
wrote:
> Hi Stephen,
>
> 2017-03-31 15:49 GMT+02:00 Stephen Riesenberg <
> stephen.riesenb...@gmail.com>:
> > Good deal. Also, a note on the number of threads issue, instead of
> > monitoring sockets, everything is in your
Marcel,
If you need help, I can look at this as well. The only issue with a fix
will be the need to either invoke the String#getBytes(...) method twice or
refactor the codec a bit. I don't know of a way to easily determine the
number of bytes in a string without just converting to bytes in your
ortantly I can still monitor the backend socket which is
> the one exposed via TCP to the rest of the world.
>
>
> 2017-03-30 21:56 GMT+02:00 Stephen Riesenberg <
> stephen.riesenb...@gmail.com>:
> >...
> > Though I'm not sure what you mean by "I would like t
Hello,
I'd like to announce the first release of jzmq-api,
org.zeromq/jzmq-api-0.1.0 on Maven Central. Keep in mind this API is still
in its infancy, but with time will begin to formalize.
See some of the recent changes here:
https://github.com/zeromq/jzmq-api/blob/master/CHANGELOG.md
Download
It obviously gets complicated in a hurry, but to add to that:
Can you create a broker per scaling group, which subscribes to the relevant
topic and uses push sockets to load balance automagically to workers? It
shouldn’t get overloaded if it’s just shuffling messages though it’s always
possible,
forward. How
> should this be handled? I can think of a timeout in the sink, but is there
> something better?
>
>
> Regards,
> Gyorgy
>
> On Wed, Dec 6, 2017 at 3:32 AM, Stephen Riesenberg <
> stephen.riesenb...@gmail.com> wrote:
>
>> It obviously gets compl
Hello,
I'd like to announce the release of jzmq-api v0.2.0 on Maven Central. This
release picks up great changes from JeroMQ v0.5.1 and contains a bug fix
for the frame builder.
See some of the recent changes here: https://github.com/zeromq/jzmq-api
/blob/master/CHANGELOG.md
Download it here:
Hello,
I'd like to announce the first release of node-red-contrib-zyre (v0.0.1) on
npm.
https://www.npmjs.com/package/node-red-contrib-zyre
https://flows.nodered.org/node/node-red-contrib-zyre
https://github.com/InSourceSoftware/node-red-contrib-zyre
If you're not familiar with Node-RED, this
d for developing
> some shared conventions.
>
>
> In any case, having this new Zyre layer in place goes a far way to
> making such a display. Nice job!
>
>
> Cheers,
> -Brett.
>
> [1] https://brettviren.github.io/zio/node.html (see also "port" and
> "peer"
Sorry for the late reply. But I will be glad to help as well. I have
released to maven central for zeromq org in the past. Is there a cadence
for releases or typically as needed?
On Wed, May 12, 2021 at 12:39 PM Doron Somech wrote:
> I'm actively using JeroMQ (and contributing), I would help us
Hi all,
I noticed that jzmq-api is listed as a public archive. I know it hasn’t
been updated in a bit but I’m wondering what the reason for this is?
https://github.com/zeromq/jzmq-api
Thanks,
Steve
___
zeromq-dev mailing list
19 matches
Mail list logo
