Comments on: ZeroMQ an introduction http://nichol.as/zeromq-an-introduction Sat, 21 Jan 2012 14:27:36 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: sidhttp://nichol.as/zeromq-an-introduction#comment-68250 sid Sun, 04 Dec 2011 18:52:19 +0000 http://nichol.as/?p=606#comment-68250 great article , thanks for all the effort. much appreciated. great article , thanks for all the effort. much appreciated.

]]> By: Continuous Education « IgorShare Webloghttp://nichol.as/zeromq-an-introduction#comment-67749 Continuous Education « IgorShare Weblog Tue, 29 Nov 2011 22:19:42 +0000 http://nichol.as/?p=606#comment-67749 [...] ZeroMQ an introduction [...] [...] ZeroMQ an introduction [...]

]]> By: Alexhttp://nichol.as/zeromq-an-introduction#comment-64547 Alex Wed, 16 Nov 2011 15:08:35 +0000 http://nichol.as/?p=606#comment-64547 Thanks for the article, it is very straightforward and the examples are very helpful.I've heard about ZeroMQ a while ago, but their site lacked the examples you provided. Now I think I'll introduce a new assignment for my students and let them create something based on this mechanism.One thing about ZeroMQ is that the naming is inconsistent. Some call it zmq, some call it 0mq or ØMQ - the name is ok, but it is inconvenient when you want to search discussions about it. Which keywords to use? This will probably bite them in the future. Thanks for the article, it is very straightforward and the examples are very helpful.

I’ve heard about ZeroMQ a while ago, but their site lacked the examples you provided. Now I think I’ll introduce a new assignment for my students and let them create something based on this mechanism.

One thing about ZeroMQ is that the naming is inconsistent. Some call it zmq, some call it 0mq or ØMQ – the name is ok, but it is inconvenient when you want to search discussions about it. Which keywords to use? This will probably bite them in the future.

]]> By: Nicholas Piël » ZeroMQ an introduction | FRANCESCO DI FUSCOhttp://nichol.as/zeromq-an-introduction#comment-62238 Nicholas Piël » ZeroMQ an introduction | FRANCESCO DI FUSCO Mon, 14 Nov 2011 06:06:57 +0000 http://nichol.as/?p=606#comment-62238 [...] Nicholas Piël » ZeroMQ an introduction. Rate this: Share this:TwitterFacebookStumbleUponPrintEmailLinkedInLike this:LikeBe the first to like this post. This entry was posted in Networking by francescodifusco. Bookmark the permalink. [...] [...] Nicholas Piël » ZeroMQ an introduction. Rate this: Share this:TwitterFacebookStumbleUponPrintEmailLinkedInLike this:LikeBe the first to like this post. This entry was posted in Networking by francescodifusco. Bookmark the permalink. [...]

]]> By: Simonhttp://nichol.as/zeromq-an-introduction#comment-62010 Simon Mon, 14 Nov 2011 00:12:26 +0000 http://nichol.as/?p=606#comment-62010 Thanks, this is an very useful article. Thanks, this is an very useful article.

]]> By: async I/O News » ZeroMQ an introductionhttp://nichol.as/zeromq-an-introduction#comment-42387 async I/O News » ZeroMQ an introduction Mon, 24 Oct 2011 15:09:06 +0000 http://nichol.as/?p=606#comment-42387 [...] Read full article Categories: Async I/O, MQ, Real-Time Web Tags: ZeroMQ /* [...] [...] Read full article Categories: Async I/O, MQ, Real-Time Web Tags: ZeroMQ /* [...]

]]> By: CaptainSmileyhttp://nichol.as/zeromq-an-introduction#comment-36408 CaptainSmiley Sat, 01 Oct 2011 04:25:29 +0000 http://nichol.as/?p=606#comment-36408 I see two smilies in the Pipelining image I see two smilies in the Pipelining image

]]> By: Nicolaihttp://nichol.as/zeromq-an-introduction#comment-35855 Nicolai Thu, 15 Sep 2011 03:55:46 +0000 http://nichol.as/?p=606#comment-35855 You are a natural teacher and the lesson is much appreciated. Even if I weren't interested in the topic, I'd have been glad to stumble here if only to see a civil discussion of pros and cons related to new technology. I can't remember the last time I saw a blog's writer thank someone for providing somewhat tendentious comments/benchmarks.. The python code examples and the diagrams were an added bonus to an already great lecture, but I will remember your quote about the shipbuilder for a long time. I think you will have good luck building your ship. You are a natural teacher and the lesson is much appreciated. Even if I weren’t interested in the topic, I’d have been glad to stumble here if only to see a civil discussion of pros and cons related to new technology. I can’t remember the last time I saw a blog’s writer thank someone for providing somewhat tendentious comments/benchmarks.. The python code examples and the diagrams were an added bonus to an already great lecture, but I will remember your quote about the shipbuilder for a long time. I think you will have good luck building your ship.

]]> By: Courtneyhttp://nichol.as/zeromq-an-introduction#comment-35767 Courtney Fri, 09 Sep 2011 21:43:34 +0000 http://nichol.as/?p=606#comment-35767 This is an excellent introduction. Thank you for the write up. When I first heard about zmq I was under the impression it acted as a server. I don't think i've been more wrong in my life. Anyway, it was a great intro and Its made clear to me quite a few things that had a question mark next to it. Thanks again This is an excellent introduction. Thank you for the write up. When I first heard about zmq I was under the impression it acted as a server. I don’t think i’ve been more wrong in my life. Anyway, it was a great intro and Its made clear to me quite a few things that had a question mark next to it.
Thanks again

]]> By: Petrhttp://nichol.as/zeromq-an-introduction#comment-35605 Petr Thu, 25 Aug 2011 15:26:57 +0000 http://nichol.as/?p=606#comment-35605 I have read Request Reply paradigm description and would like to clarify a couple concerns. Nicholas, to automatically balance requests you suggest connecting one more socket on client side. Requests balancing on client side? Client should be aware about all servers? Who will support the server list on client side? How to manage clients if you have access to server side only? Are you serious about requests balancing on client side? Balance the requests over an extra server (on diagram named as Queue) – bottleneck, isn’t it? I have read Request Reply paradigm description and would like to clarify a couple concerns.
Nicholas, to automatically balance requests you suggest connecting one more socket on client side. Requests balancing on client side?
Client should be aware about all servers? Who will support the server list on client side? How to manage clients if you have access to server side only?
Are you serious about requests balancing on client side?
Balance the requests over an extra server (on diagram named as Queue) – bottleneck, isn’t it?

]]>