Thanks, that was the problem. The broken one had 4.0.3 and the working one
had 2.2.0
On Sun, Dec 29, 2013 at 12:09 PM, Min RK wrote:
> what is zmq.zmq_version() on each?
>
> -MinRK
>
> On Dec 29, 2013, at 0:01, Thomas Johnson
> wrote:
>
> Consider the following simple program:
> #CUT HERE-
On Sun, Dec 29, 2013 at 11:13 AM, artemv zmq wrote:
> I can implement TTL myself, making it being as a part of message, _but_ I
> don't want to do that, because, TTL is low level thing, so fixing it at
> higher level would bring more problems, I suppose.
Do you know, or do you suppose? If you k
On Sun, Dec 29, 2013 at 12:04 PM, Bjorn Reese wrote:
> ZeroMQ is an open-source community, which is sufficient to be an entity
> in the eyes of GSoC. Somebody from the ZeroMQ, preferably one of the
> leading figures, has to submit a proposal for participation as a
> mentoring organization. See (e
On Sat, Dec 28, 2013 at 3:24 PM, Daniel Krikun wrote:
> I'm not saying the patterns suck, they surely do not, personally I think
> they are very helpful, but they are not perfect. Maybe plain udp can be
> easier to grasp.
The point is that you can use higher level semantics like pub-sub and
then
what is zmq.zmq_version() on each?
-MinRK
> On Dec 29, 2013, at 0:01, Thomas Johnson wrote:
>
> Consider the following simple program:
> #CUT HERE
> #!/usr/bin/python
> import zmq
>
> context_push = zmq.Context(1)
> socket_push = context_push.socket(zmq.PUSH)
>
> context_pull = zmq.Co
Ah the Python is great!
Brian Knox wrote:
>I apologize in advance. I really just absolutely could not resist...
>
>"Woman: I didn't know we had a king. I thought we were an autonomous
>collective.
>Dennis: You're foolin' yourself! We're living in a dictatorship. A
>self-perpetuating autocracy
I apologize in advance. I really just absolutely could not resist...
"Woman: I didn't know we had a king. I thought we were an autonomous collective.
Dennis: You're foolin' yourself! We're living in a dictatorship. A
self-perpetuating autocracy in which the working class...
Woman: Oh, there you
ZeroMQ's internal queues allow you to send messages asynchronously, and allow
ZeroMQ to increase throughput at the cost of a little latency by batching
messages. They aren't in my opinion designed to be a persistent message queue
system in the way you describe - and they would need a lot more f
On 2013-12-29 12:04, Bjorn Reese wrote:
> On 12/29/2013 02:15 AM, Pieter Hintjens wrote:
>> Not sure what's meant by ZeroMQ being there. We're not an entity,
>> just
>> a random group of people with sometimes coinciding interests. What
>> would it take for ZeroMQ to "be there"?
>
> ZeroMQ is an op
On 29 Dec 2013, at 9:33 pm, artemv zmq wrote:
> hi Matt,
>
> The game UI does handle response timeout. Tomcat just transfers traffic
> back and forth.
But if the message is sent asynchronously to the betting service, then where
does the timeout come from?
-Matt
___
Dear list,
I’ve been playing around with how to ensure that a service has processed all
messages that it has received (in the receiving socket queue) before shutting
down. In particular, I’m using the rbczmq ruby bindings, so this question is
also to see if those bindings are consistent with ot
hi Matt,
The game UI does handle response timeout. Tomcat just transfers traffic
back and forth.
2013/12/29 Matt Connolly
> If the Tomcat service (layer 1) sends messages asynchronously to the
> betting service (layer 2), then how is it possible to timeout the response
> back to the iOS/Andr
On 12/29/2013 02:15 AM, Pieter Hintjens wrote:
> Not sure what's meant by ZeroMQ being there. We're not an entity, just
> a random group of people with sometimes coinciding interests. What
> would it take for ZeroMQ to "be there"?
ZeroMQ is an open-source community, which is sufficient to be an en
If the Tomcat service (layer 1) sends messages asynchronously to the betting
service (layer 2), then how is it possible to timeout the response back to the
iOS/Android app (layer 0)?
-Matt
On 29 Dec 2013, at 8:13 pm, artemv zmq wrote:
> hi Pieter,
>
> > You're still not explaining what probl
hi Pieter,
> You're still not explaining what problem this solves
Ok. Here's the problem which I faced recently. Here's appl. architecture
(to keep discussion focused):
iOS/Android (game ui) Tomcat <> bet_service .
There are three layers (from left to right): game UI (
Consider the following simple program:
#CUT HERE
#!/usr/bin/python
import zmq
context_push = zmq.Context(1)
socket_push = context_push.socket(zmq.PUSH)
context_pull = zmq.Context(1)
socket_pull = context_pull.socket(zmq.PULL)
socket_pull.bind("tcp://127.0.0.1:2000")
socket_push.connect("
16 matches
Mail list logo
