I have test code that works in a test scenario and from one server
platform, but the same code's call to ZMQ.context(NUM_THREADS) simply
blocks its thread on a different server platform. The difference is in the
"flavor" of server for handling differing workloads. Any suggestions
gratefully recei
I like the idea of having a very thin, high performance JNI wrapper on top
of libzmq. I just start working a version here:
https://github.com/trevorbernard/zmq-jni
It will likely stay in my personal github account until it stabilizes. It's
able to send/recv but lacks all kinds of polish. Here is a
> There is a method in the class where 1) the context is retrieved, 2) a
socket created, 3) message published and 4) socket closed.
Socket close command is processed asynchronously by reaper thread, and it
seems like you don't give it enough time to release resources.
Creating/destroying a socket
I use pub/sub topology with one subscriber and one publisher (for now).
Publisher is a java class where context is a static class variable. It is
instantiated in the class constructor. There is a method in the class where
1) the context is retrieved, 2) a socket created, 3) message published and
4)
I'm very excited because I think I found a way to accomplish on
Windows what I'd managed to get to work for me on POSIX, more or less.
This at least compiles and if I'm correctly understanding the
documentation for these functions that I've found online, then this
might even do the Right Thing (TM)
@Michael Haberler: recall the last one, it is covered
On Tue, Aug 13, 2013 at 8:23 PM, Daniel Krikun wrote:
> For the sender, the situation is transparent, however, it so happens that
> for ZMQ_PUB if hwm is reached it indeed drops the message so it should work
> for you, right?
>
>
> On Tue, Au
For the sender, the situation is transparent, however, it so happens that
for ZMQ_PUB if hwm is reached it indeed drops the message so it should work
for you, right?
On Tue, Aug 13, 2013 at 6:59 PM, Michael Haberler wrote:
>
> Am 13.08.2013 um 17:29 schrieb Daniel Krikun :
>
> > I have almost fi
Am 13.08.2013 um 17:29 schrieb Daniel Krikun :
> I have almost finished the feature, in the mean time, it evolved as follows:
> -- it will be available for ZMQ_PULL, ZMQ_SUB and ZMQ_DEALER sockets
> -- it is activated using ZMQ_CONFLATE socket option at the receiver side
> -- currently, multi-par
I have almost finished the feature, in the mean time, it evolved as follows:
-- it will be available for ZMQ_PULL, ZMQ_SUB and ZMQ_DEALER sockets
-- it is activated using ZMQ_CONFLATE socket option at the receiver side
-- currently, multi-part messages would not be supported
-- currently, would not
Damien Kick mac.com> writes:
> Well, the reason that I want to integrate with Boost.Asio is more
> for getting its implementation of the reactor pattern "for free",
> including timers, etc.
And I've pretty much resigned myself that in this case, what's good
for the POSIX is certainly not good fo
Now even the curvezmq ebuild works and tests pass.
Le 10/08/2013 16:11, Laurent Alebarde a écrit :
Sorry for my lack of precision : these ebuilds are live ones i.e. :
they fetch from the git repository.
Le 10/08/2013 16:09, Laurent Alebarde a écrit :
These ebuilds can be found here :
* li
Thanks, will do that.
On Tue, Aug 13, 2013 at 2:22 AM, Pieter Hintjens wrote:
> Take a look at the filemq.java main program.
>
> On Mon, Aug 12, 2013 at 8:09 PM, ashwini ramamurthy
> wrote:
> > Hi Pieter,
> >
> > Thanks for your quick response. Where can i find the example your talking
> > abo
I've been using ZeroMQ to distribute frames from video streams for
processing and for some of my use cases this feature would be of great
interest. I'll happily be a test victim of a patch.
Brian
On Tue, Aug 13, 2013 at 4:27 AM, Michael Haberler wrote:
> Daniel,
>
> Am 07.06.2013 um 11:53 schr
The 0x00 0x00 sent by both pub and sub is the 0-length identity frame. I.e.
no explicitly set identity.
I made a mistake in my previous mail, "final-short" is 2 bytes long, the
length is part of it.
On Aug 13, 2013 6:00 PM, "Shan Wang" wrote:
> Thanks,
>
> ** **
>
> That document makes sense
Thanks,
That document makes sense. But do you know in what situation the SUB socket can
send 0x00 0x00 to PUB? Does that mean a final short with length 0?
Also why PUB send 0x00 0x00 to SUB after the signature?
One thing I forgot to mention, once the SUB socket is broken, it can not
recover, m
Daniel,
Am 07.06.2013 um 11:53 schrieb Daniel Krikun :
> Hi all,
>
> I have a setup, where a server does graphics rendering based on client
> requests, that is, clients send geometric data (position, orientation,
> etc.) and the server runs in cycles: process incoming messages and do
> some rend
Am 12.08.2013 um 02:36 schrieb Steven McCoy :
> On 9 August 2013 13:43, Michael Haberler wrote:
> it's unclear how I would replicate the following queue usage:
>
> A queue of pending commands is checked periodically for limit violations;
> however, the queue entries are not consumed
>
> You m
17 matches
Mail list logo
