hi,
Recently the collegue from SFO asked me exactly the same question as
you. Here's your steps.
1. You need 10.9. Since MacBook I tested on was on Maverick. Nobody
had 10.8.5 in office, sorry.
2. Get homebrew. This is package installer for OSX. Install it: ruby
-e "$(curl -fsSL https://raw.gi
Feel free to share you opinion, post a comments and any objections.
In two words: this is abstraction around JZMQ itself. Author read a
guide, played with ZMQ, and decided to create some invaluable
form-and-function for JZMQ users.
JZMQ-SUPPORT provides:
- same tricks as you did in JZMQ, but wit
https://github.com/artem-v/jzmq-support
Here's a link
2013/10/24 Artem Vysochyn :
> Feel free to share you opinion, post a comments and any objections.
>
> In two words: this is abstraction around JZMQ itself. Author read a
> guide, played with ZMQ, and decided to create some
Hi Howard,
Seems like you need something which could render "sticky" behaviour
between N-clients and M-workers. Right? If so, keep reading.
1. Read, understand and love socket identities.
2. Use ROUTER-ROUTER as a device-in-the-middle. I call it LRU-device.
3. Use socket identities on client side
, -1 on error
*/
public native int recv (byte[] buffer, int offset, int len, int flags);
Have no more questions :)
2013/10/3 Artem Vysochyn :
> hi Trevor,
>
> Thanks for posting this. Very nice.
>
> Still curious. Does it mean that using DirectByteBuffer only m
tance() {
> return ByteBuffer.allocateDirect(4096);
> }
> };
>
> On Wed, Oct 2, 2013 at 12:30 PM, Artem Vysochyn
> wrote:
>> hi Trevor,
>>
>> Can you past example(s) of how you use DirectByteBuffer in jzmq? pls.
>>
>> 2013/10/2 Trevor Be
Hi Kieran,
>>>The way it's done currently means that if we add new functionality, it
>>>has to be replicated at all points, rather than a ZMQ solution, where
>>>just at the client and worker would be aware of the message format,
>>>everything in between would just be for moving messages.
I would
hi Trevor,
Can you past example(s) of how you use DirectByteBuffer in jzmq? pls.
2013/10/2 Trevor Bernard :
> I do that very thing with a different method signature.
>
> https://github.com/trevorbernard/zmq-jni/blob/master/src/main/c%2B%2B/zmq.cpp#L169
>
> I've had some success with preallocating
Hi Pieter,
Thanks a lot. Now I see.
2013/10/2 Pieter Hintjens :
> On Tue, Oct 1, 2013 at 11:01 PM, Artem Vysochyn
> wrote:
>
>> Still totaly confused... Why need to port something on something? Why
>> then not create php-port or python-port?
>
> There is a .Net por
Still totaly confused... Why need to port something on something? Why
then not create php-port or python-port?
What bothers most, if this is "a port", then it should mandate "what
exactly is currently supported and what is not, what is supported with
limitations", and so on.
Or should I just beli
Actually, the question in subj.
Q1: What are compeling reasons one should know so that they could turn
him into JeroMQ?
Q2: What's true about JeroMQ:
- better supported?
- community more responsive?
- community has quicker turnaround (in terms of features)?
- battle tested (has prod deployments)?
Hi Pieter,
JeroMQ. I was on http://zeromq.org/bindings:java and could not find
any info on JeroMQ.
Q: is this offcially maintained zmq java binding/port/whatever?
Thanks
2013/10/1 Pieter Hintjens :
> Nick,
>
> The general advice is to use JeroMQ to start with and move to JZMQ
> later when / i
hi zmq-ers,
Im' curios, why zmq socket provides next settings?
setTCPKeepAlive()
setTCPKeepAliveCount()
setTCPKeepAliveInterval()
setTCPKeepAliveIdle()
As I understood, zmq hides from end-user the fact that it reconnects
him. So why keep_alive is needed? :|
__
I was wrong about detecting sent/no-sent messages on PUB socket
using poller and POLLOUT events. I have muddle up this with PUSH,
because for PUSH this approach works.
Sorry for confusion
2013/9/26 Pieter Hintjens :
> On Thu, Sep 26, 2013 at 8:08 PM, Artem Vysochyn
> wrote:
>
Thank you Matt.
2013/9/27 Matt Connolly :
> No, ZMQ sockets never generate ZMQ_POLLERR.
>
> On 27/09/2013, at 8:06 AM, Artem Vysochyn wrote:
>
>> hi Matt,
>>
>> Thanks for reply. But if I use only ZMQ socket everywhere in
>> application, then should po
I would much appreciate for the advice on method signature.
I want to make an api (in java) which could do bulk_send() and
bulk_recv() ... Not very sophisticated riddle, but just want to choose
most compact and clear method definitions.
Thanks
-artemv
__
ges or data received on a plain old socket (pipe, tcp or stdin) and
> detect errors on that plain old socket.
>
> -Matt
>
> On 27 Sep 2013, at 6:59 am, Artem Vysochyn wrote:
>
>> Sorry, the typo: >>>> ... driving non-ZMQ-sockets ...
>>
>> 2013/9/26 Art
Sorry, the typo: >>>> ... driving non-ZMQ-sockets ...
2013/9/26 Artem Vysochyn :
> hello there,
>
> I'm reading the api guide, http://api.zeromq.org/3-2:zmq-poll, and a
> bit confused by definition ZMQ_POLLERR.
>
> Here it's:
>>>
> For standar
hello there,
I'm reading the api guide, http://api.zeromq.org/3-2:zmq-poll, and a
bit confused by definition ZMQ_POLLERR.
Here it's:
>>
For standard sockets, this flag is passed through zmq_poll() to the
underlying poll()system call and generally means that some sort of
error condition is present
Aayush :)
What you are describing here is extermely cool, but that
"architecture" you described (I read it very carefully) renders the
fact that you did not really read the guide, or just "scratched a
surface".
Seriously, read the guide.
2013/9/26 aayush gupta :
> Hi,
>
> I am a newbie to usin
b and sub but i see no memory growth that i might
>> associate with a backlog.
>>
>> On 26 September 2013 17:01, Artem Vysochyn wrote:
>>> hi Renato,
>>>
>>> ZMQ api manual is very clear about PUB/SUB:
>>>>>
>>> A socket of type ZMQ_PUB
hi Renato,
ZMQ api manual is very clear about PUB/SUB:
>>
A socket of type ZMQ_PUB is used by a publisher to distribute data.
Messages sent are distributed in a fan out fashion to all connected
peers.
When a ZMQ_PUB socket enters the mute state due to having reached the
high water mark for a subsc
gh workers to keep up with the messages coming from
> the clients. If this is the case, isn’t the answer more workers?
>
> In either case can’t you monitor the scenario by knowing how many messages
> you have received and how many replies you have sent back?
>
> Regards,
> Matt
>
learn the basics by working through the examples, before
> attempting anything complex.
>
> On Tue, Sep 24, 2013 at 4:15 PM, Artem Vysochyn
> wrote:
> > I'm working on creating top-notch rpc-framework (further RPCF) on the
> base
> > of jzmq/zmq and faced with seriou
I'm working on creating top-notch rpc-framework (further RPCF) on the base
of jzmq/zmq and faced with serious design issue. Here's the deal, in
my RPCF I'm going to use devices, especially LRU-device (via ROUTER-ROUTER
mechanism), and more trivial FAIR-device (via ROUTER-DEALER mechanism).
Regardl
; rotate messages out. PUB does multicast. SUB/PULL/DEALER rotates
> messages in. ROUTER rotates in, and uses addressed output. PAIR always
> sends to its unique peer, if any.
>
> -Pieter
>
> On Tue, Sep 24, 2013 at 1:40 PM, Artem Vysochyn
> wrote:
> > I was reading a g
I was reading a guide, it says you can take single socket and connect it to
multiple addresses, and bind to multiple addresses. While this is, without
doubts, really cool, guide doesn't show much details on how one can benefit
from being bound on multiple addresses. That's why I'm asking community,
a single socket, rather than trying to avoid
> this by creating new sockets over and over. Your design is mixing
> layers in a way that will not work, and goes against the basic zen of
> how to use ZeroMQ.
>
> Hope that helps.
>
> -Pieter
>
>
> On Fri, Sep 20, 2013 at 6:
s the point about router-dealer is the intelligence sits on the
> router side, not the dealer side. One router, many dealers. Perhaps
> you are using these the wrong way around?
>
> On Fri, Sep 20, 2013 at 5:45 PM, Artem Vysochyn
> wrote:
> > Appreciate for prompt response, Pie
No problem et al. In general, I really love ZMQ, it teaches me always
think towards finding most simple-and-effective solutions. But it's always
"it depends" on what ppl mean under "clumsy way".
And when I originally wrote a code which has been sending correlation_id
along inside message, after
Have a next problem:
I'm working on generic RPC java library on the jzmq/zmq base. At the core
will be following arch:
clients own inproc DEALER/REQ and send to local inproc ROUTER-DEALER. The
latter DEALER side will be tcp, and it will propagate messages further to
the services which are tcp RO
The classic pattern is a router server that tracks client identities
> and state per dealer client.
>
> On Fri, Sep 20, 2013 at 5:21 PM, Artem Vysochyn
> wrote:
> > Have a next problem:
> >
> > I'm working on generic RPC java library on the jzmq/zmq base. At
32 matches
Mail list logo