Interacting with ZeroMQ from the browser

I like delivering ZeroMQ content to the browser (I have even written my own little WebSockets server to deliver ZeroMQ-pubsub meessages to my webapp), but I'm not sure I understand what the use for STOMP or NullMQ is, here. Is STOMP just used for to translate some bits to ZeroMQ frame terms and NullMQ used as the WebSockets-to-ZeroMQ broker? Why is this better than <a href="https://github.com/tailhook/zerogw" rel="nofollow">https://github.com/tailhook/zerogw</a>?

"ZeroMQ’s actual C library (libzmq) is just an implementation detail."<p>That's a spot on. It doesn't really matter whether you are using ZeroMQ, NullMQ or raw HTTP.<p>It's like OO-programming: You can write OO program in any language.<p>Same way, you can do distributed messaging on top of any transport layer.

Jeff and Bulat - this is fascinating and timely. Just this week I've been experimenting with bridging (Apollo) STOMP with <a href="https://github.com/wandenberg/nginx-push-stream-module" rel="nofollow">https://github.com/wandenberg/nginx-push-stream-module</a> and getting what appears to be similar results. Neat stuff, and I'm half tempted to write an nginx-STOMP bridge to save a few layers of indirection.

Mongrel2.org anyone?

Neat. I've wanted ZeroMQ in my browser.<p>I checked the README file for a license, but instead it says "ZeroMQ in your brower, yo!" Which tells me that:<p>1. I can't use it.<p>2. The author is 12.<p>3. It probably doesn't work.