sustrik

4 ms·

1.
by sustrik 11y ago
maybe that's the solution to the suburbia problem. move the people downtown and let the suburbs rot off.
2.
by sustrik 15y ago
Giants protecting minnows? Reminds me of middle ages. You swear allegiance to the local lord which in turn protects you from other lords.
3.
Patents Considered Evil(ipocracy.com)
4 points by sustrik 15y ago|0 comments
4.
by sustrik 15y ago
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
5.
by sustrik 15y ago
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
6.
by sustrik 16y ago
Not really. Compare 0MQ's wire protocol: http://rfc.zeromq.org/spec:2 and STOMP: http://stomp.codehaus.org/Protocol
7.
by sustrik 16y ago
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.
8.
by sustrik 16y ago
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.
9.
by sustrik 16y ago
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-e
10.
by sustrik 16y ago
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.
11.
by sustrik 16y ago
That's the point. Single 0MQ socket is able to communicate with multiple peers.
12.
by sustrik 16y ago
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."
13.
by sustrik 17y ago
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: http://api.zeromq.org/zmq_pgm.html