The main use case from my point of view would be getting the benefits of
ZMQ inproc messaging patterns coupled with the expected C++ object
semantics provided by QT signals.
The ability to give thread affinity to a QObject, effectively making any
slot on that object be called in the same thread no
Mapping ZeroMQ sockets to Qt signals/slots would be wild. :) None of the
existing libs attempt anything like this. I'd have to think more about
the use cases.
On 01/27/2014 01:39 PM, Lindley French wrote:
> Question: One of the drawbacks of QT's signals and slots mechanism
> (which is otherwise
Question: One of the drawbacks of QT's signals and slots mechanism (which
is otherwise great) is that it supports many-to-one (like ZMQ pull or sub)
and one-to-many (like ZMQ pub), but it does't support one-to-any (like ZMQ
push).
Is there anything in any of these projects that addresses this in a
Hi Goswin,
On 01/27/2014 03:46 AM, Goswin von Brederlow wrote:
> On Sun, Jan 26, 2014 at 11:34:13PM -0800, Justin Karneges wrote:
>> There are a few options:
>>
>> https://github.com/wttw/zeromqt
>> https://github.com/jonnydee/nzmqt
>> https://github.com/jkarneges/qzmq
>>
>> It sounds like you've
On Sun, Jan 26, 2014 at 11:34:13PM -0800, Justin Karneges wrote:
> There are a few options:
>
> https://github.com/wttw/zeromqt
> https://github.com/jonnydee/nzmqt
> https://github.com/jkarneges/qzmq
>
> It sounds like you've downloaded zeromqt. The project should contain
> README.markdown.
>
>
There are a few options:
https://github.com/wttw/zeromqt
https://github.com/jonnydee/nzmqt
https://github.com/jkarneges/qzmq
It sounds like you've downloaded zeromqt. The project should contain
README.markdown.
I am the author of QZmq and can help with it if you'd like.
On 01/26/2014 11:11 PM,
