sustrik
Re:The two Detroits: a city both collapsing and gentrifying at the sam...
on Tuesday September 29, 2015 @03:41AM (#10295040)
maybe that's the solution to the suburbia problem. move the people downtown and let the suburbs rot off.
Re:Patents: Can the giants protect the minnows?
on Sunday September 11, 2011 @02:01PM (#2984319)
Giants protecting minnows? Reminds me of middle ages. You swear allegiance to the local lord which in turn protects you from other lords.
Re:ZeroMQ =/= Erlang
on Friday July 01, 2011 @02:47AM (#2717284)
One thing to keep in mind is that 'multithreading magic' article was written when 0MQ was viewed to be equivalent to other MQ systems. The idea of using 0MQ for building multi-threaded apps was really surprising and non-obvious for a lot of people back then.
So, the article focuses on 0MQ =/= SomeGenericMQ and doesn't stress the 0MQ =/= Erlang point of view.
Re:ZeroMQ Pub Sub: How does it work?
on Friday June 17, 2011 @12:22PM (#2666085)
There's a new functionality in dev version (3.0) that allows for dissemination of subscriptions across the network. The whitepaper is here: http://www.250bpm.com/pubsub
Re:ZeroMQ: Modern & Fast Networking Stack
on Sunday September 05, 2010 @07:01AM (#1664337)
Not really. Compare 0MQ's wire protocol:
and STOMP:
Re:ZeroMQ: Modern & Fast Networking Stack
on Sunday September 05, 2010 @02:17AM (#1664121)
Did existence of TCP discouraged people to write their own implementation of OSI layer 4? Not really. But those who do so are a small -- i mean really small -- minority.
Re:ZeroMQ: Modern & Fast Networking Stack
on Sunday September 05, 2010 @02:11AM (#1664111)
Speaking of AMQP/RabbitMQ there's an integration project here: http://github.com/rabbitmq/rmq-0mq. The idea is that you can use RabbitMQ as a broker for 0MQ networks.
Re:ZeroMQ: Modern & Fast Networking Stack
on Sunday September 05, 2010 @01:56AM (#1664095)
0MQ is built on good old principles the Internet stack (TCP, IP) is based upon. Thus is has tx/rx buffers. It doesn't even try to do fire-and-forget, because -- as you correctly say -- it's an leaky abstraction. Instead it aims for end-to-end reliability. And yes, moving it into kernel would make it somehow more reliable. Watch for my talk at Linux Kongress (eeptember 23rd) which deals with moving the functionality into kernel, standardisation and integration with Internet stack.
Re:ZeroMQ: Modern & Fast Networking Stack
on Sunday September 05, 2010 @01:38AM (#1664080)
That's the nature of networking. You can never differentiate between "network error" and "no response received". TCP in no better. You'll have accept that or keep with a single box.
Re:An introduction to ZeroMQ
on Friday June 25, 2010 @03:17PM (#1461797)
That's the point. Single 0MQ socket is able to communicate with multiple peers.
Re:An introduction to ZeroMQ
on Wednesday June 23, 2010 @10:58AM (#1455079)
There's no SPOF unless you create one. So the sentence should be more correct this way "ZeroMQ follows a brokerless design so that doesn't enforce single point of failure."
Re:IMatix: AMQP ‘fundamentally flawed’
on Wednesday March 31, 2010 @06:31AM (#1231383)
As for the wire protocol, there are two parts to it:
Simple framing is described here:
http://api.zeromq.org/zmq_tcp.html
Extension of the framing for multicast: