Issue here: https://github.com/zeromq/czmq/issues/2158
Also related for javascript: https://github.com/zeromq/jszmq
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
https://lists.zeromq.org/mailman/listinfo/zeromq-dev
Hey all,
I'm currently getting started with the new websockets transport. It's
not exposed in czmq but I managed to make it work.
However as it is websockets I'd like to get it to do something in a
browser as well. I have this example running which works. Although I
can't prove whether this
On Tue, Apr 20, 2010 at 09:57:42PM +0200, Pieter Hintjens wrote:
Perhaps a general solution is to move the 0MQ work to a separate
process and talk to that. It can run at full speed and queue stuff up
for the Ruby app to take when it needs it.
That is logical. However, then you need to design
On Wed, Apr 21, 2010 at 10:41 AM, Brian Candler b.cand...@pobox.com wrote:
If such a protocol existed, it would be tempting to run it directly on the
wire instead of 0MQ. Or, the local protocol could work differently (e.g.
synchronous polling for pulling newly-arrived messages out of the
Brian,
So there may be a place for a pure-ruby implementation of zmq after all.
I would definitely try not to go that way. While the wire protocol is
extremely simple, actual implementation of a messaging endpoint is
pretty complex (managing many connections, queueing, fair queueing and
load
Martin Sustrik wrote:
Well, we get that even today. The problem is that toy languages don't
implement real concurrency so that they can get stuck when interacting
with 0MQ...
Ruby is basically a single OS thread + green Ruby threads, right?
Such a design doesn't work with 0MQ, but it also
sust...@imatix.com said:
Martin Sustrik wrote:
Well, we get that even today. The problem is that toy languages don't
implement real concurrency so that they can get stuck when interacting
with 0MQ...
Ruby is basically a single OS thread + green Ruby threads, right?
Ruby 1.8 (the
On Wed, Apr 21, 2010 at 3:33 PM, Martin Sustrik sust...@imatix.com wrote:
Ruby is basically a single OS thread + green Ruby threads, right?
Language != implementation of language.
See here
http://stackoverflow.com/questions/56087/does-ruby-have-real-multithreading
11 different runtimes (not
On Apr 21, 2010, at 8:49 AM, Pieter Hintjens wrote:
On Wed, Apr 21, 2010 at 3:33 PM, Martin Sustrik sust...@imatix.com wrote:
Ruby is basically a single OS thread + green Ruby threads, right?
Language != implementation of language.
See here
On Wed, Apr 21, 2010 at 01:28:06PM +0200, Martin Sustrik wrote:
The main problem here (and that's a reoccurring issue) is the 0MQ
sockets cannot be polled on because they aren't real file
descriptors.
I can imagine a small wrapper library on top of 0MQ that would
intercept the system BSD
Brian Candler wrote:
On Wed, Apr 21, 2010 at 01:28:06PM +0200, Martin Sustrik wrote:
The main problem here (and that's a reoccurring issue) is the 0MQ
sockets cannot be polled on because they aren't real file
descriptors.
I can imagine a small wrapper library on top of 0MQ that would
* I'd also like to see some documentation of the on-the-wire protocol. I
haven't read through all the white papers yet, but I don't see it at first
glance. This is partly for idle curiosity, but also for the possibility of
implementing a pure-ruby version. I would have to understand the
On Wed, Apr 14, 2010 at 03:20:01PM +0100, Brian Candler wrote:
* I installed the gem version of the ruby bindings, which gave me
rb-zmq-0.0.6.
I installed the latest ruby bindings from
http://github.com/sustrik/rbzmq.git
(The zeromq home page shows always the http link for visiting
13 matches
Mail list logo
