> The messages are delivered into a PUSH (publish) ØMQ socket (ala Mongrel2) ... Backend subscribers use a PULL (subscribe) socket to process the SPDY stream<p>I might be fuzzy on my 0MQ knowledge and Mongrel2 but I thought PUSH/PULL are distinct socket types from PUB/SUB...
The most interesting part of this article for me is the comment from Jay Levitt about AOL's old stack. Fascinating.<p>The reimplementation side of things is one more strike against software patentry, at least.
Btw, there's another project that acts as a gatway between HTTP/WebSockets and 0MQ here: <a href="http://tailhook.github.com/zerogw/" rel="nofollow">http://tailhook.github.com/zerogw/</a><p>Also, there's an attempt for 0MQ module for Nginx: <a href="https://github.com/FRiCKLE/ngx_zeromq" rel="nofollow">https://github.com/FRiCKLE/ngx_zeromq</a>
SPDY is here to increase efficiency between browser and server (this is sometimes called scaling). 'Dynamic network typologies' as presented is moving the network routing stack to a software CPU. Not sure I would bridge these two technologies together to solve my 'interesting worker topology patterns'. This is classic top down design.
On one hand, you have tcp, which already allows you to multiplex multiple streams, every bit of software understands it, and your back office web application servers fully support it. Yes, it has limitations (slow start applying to individual streams instead of all the streams between two computers seems to be the primary one), but instead of trying to fix it (which admittedly would take a lot of work and would be a slow process), you take a single tcp stream and implement multiplexing all over again, now you have to work support into all your applications from top to bottom. Not surprisingly, this also takes a lot of work and is slow process.
Should we be expecting in a few years, that web sockets will be advanced enough for us leave HTTP/1.1. behind? Aside from chat/messaging I'm not sure how web sockets can provide additional functionality from what we have now.<p>Edit: I confused web sockets with SPDY. I have to go read up on what these things actually are.
ØMQ?<p>How does one pronounce that? <i>Yur-m-k</i>?<p><a href="http://webcache.googleusercontent.com/search?q=cache:zsS5aXXWyigJ:en.wikipedia.org/wiki/%C3%98+%C3%98&cd=1&hl=en&ct=clnk&gl=uk" rel="nofollow">http://webcache.googleusercontent.com/search?q=cache:zsS5aXX...</a>