Dear all,
this is my first post to this list so please bear with my rather lengthy
thoughts.
I'm working in a financial markets environment and am currently looking
into
alternatives for near-realtime trade data message delivery (contracts or
deals, not market data ticks).
Traditionally we are
Hi Pieter,
Von: Pieter Hintjens p...@imatix.com
I'll answer this very briefly. Yes, you can build what you need on top
of ZeroMQ and hit your goals of cost, openness, and performance.
Development effort will be reasonable. Yes, we will provide support,
during and after this process. Please
Hi Sabri,
zeromq-dev-boun...@lists.zeromq.org schrieb am 18.09.2014 19:07:02:
Von: Sabri Skhiri sabri.skh...@gmail.com
We detected the necessity
to create a lightweight and elastic bus on top of ZeroMQ in the end of
2010. At that time we started an internal research project and we
published
zeromq-dev-boun...@lists.zeromq.org schrieb am 14.10.2014 11:08:26:
Von: Pieter Hintjens
[...]
- 4.1.0 rc1, with many changes
All on http://zeromq.org/intro:get-the-software as usual.
Also:
* The stabilization fork for 4.1.x is at
https://github.com/zeromq/zeromq4-1
...
Hi,
zeromq-dev-boun...@lists.zeromq.org schrieb am 13.10.2014 15:36:38:
Von: Pieter Hintjens
Mohit,
I've started on a new broker project,
https://github.com/Malamute/malamute, which aims to do what you're
asking for.
If you would like to read the description and tell me how closely it
Pieter,
thanks for your clarifications. Some follow-up coments/questions:
Von: Pieter Hintjens
A stream is a convenient top-level isolation. Typically one stream
serves one application. Within streams, readers choose subjects they
are interested in, using pattern matching.
Ok. Still more
Von: Pieter Hintjens
By magic coincidence I'm sketching out a proposal for reliable pub-sub.
https://github.com/zeromq/zeps
What would be the appeal of having a centralized ZeroMQ broker as opposed
to just using some existing out-of-the box solution, probably (I almost
dare not say it ;-)
Hi,
I realize I'm sometimes confused by terms used by myself and others.
So, in an attempt to clarify my thoughts, first and foremost to myself, by
writing them down here's how I tend to think about pub-sub messaging:
(0) Publish-subscribe (pub-sub) messaging:
- one or many sender(s) publish
Hi Ben,
thanks for your thoughts on this.
Von: Ben Kloosterman
100% guaranteed delivery is a myth .. pull the cable out and don't
put it back. QED
100% everything is a myth ;-).
In most cases attempts at guaranteed delivery create more bugs and
problems then non guaranteed delivery. I
Von: Dorvin
W dniu 2014-10-20 09:21, Holger Joukl pisze:
As always, it's a tradeoff you have to make: Higher QoS usually
means lesser throughput, much like memory vs speed tradeoffs.
Side note: Please don't confuse reliability and QoS. QoS has nothing
to do with reliability. It's
Hi,
not being an authority on the subject, but got curious...
> I'm trying to understand the ZMTP protocol, so I was going through
> the RFC for version 1.0 [0]. It states that:
> The following diagram shows the layout of a frame with a length of 1
> to 254 octets:
>
Hi,
(silent lurker on this list and no curve experience at all, but...)
"zeromq-dev" schrieb am 13.10.2016
08:59:15:
> I would like to swap the keys, so, the publisher should encrypt the data
> with his public key, and the subscribers should decrypt the data
I'm but a silent lurker here, but I couldn't resist:
https://hintjens.gitbooks.io/scalable-c/content/preface.html: "Why not C+
+?"
;-)
I'm not sure if this is still the case today but in my (rather outdated)
experience it can be difficult next to impossible to use C++ libraries
built with a
13 matches
Mail list logo