1. NullMQ
ZEROMQ SEMANTICS IN THE BROWSER
Jeff Lindsay Bulat Shakirzyanov
@progrium @avalanche123

4. libzmq

5. High-level patterns
libzmq

6. Philosophy
High-level patterns
libzmq

7. Philosophy
High-level patterns
libzmq

8. Philosophy
High-level patterns
API / Semantics
libzmq

9. Toolkit for building messaging systems...

10. Toolkit for building messaging systems...
...behind your firewall

11. Toolkit for building messaging systems...
...behind your firewall
...not for customers

12. Toolkit for building messaging systems...
...behind your firewall
...not for customers
...certainly not with the browser

13. WITH VOICE
MAKE & RECEIVE
PHONE CALLS
SEND & RECEIVE
TEXT MESSAGES
INSTANTLY BUY
PHONE NUMBERS
ADD VOICE TO
WEB & MOBILE APPS

17. Browser Browser

18. ZeroMQ in the
browser?

19. ZeroMQ in the
browser?
• libzmq is a C++ library

20. ZeroMQ in the
browser?
• libzmq is a C++ library
• Browser extension not viable

21. ZeroMQ in the
browser?
• libzmq is a C++ library
• Browser extension not viable
• ZMTP is not valuable by itself

22. Let’s say we did...

23. Let’s say we did...
• Security?

24. Let’s say we did...
• Security?
• Skip existing auth infrastructure

25. Let’s say we did...
• Security?
• Skip existing auth infrastructure
• Need to make something up

26. Let’s say we did...
• Security?
• Skip existing auth infrastructure
• Need to make something up
• Direct connections?

27. Let’s say we did...
• Security?
• Skip existing auth infrastructure
• Need to make something up
• Direct connections?
• Lots of open connections, open ports

28. Let’s say we did...
• Security?
• Skip existing auth infrastructure
• Need to make something up
• Direct connections?
• Lots of open connections, open ports
• Just not “web friendly”

29. Philosophy
High-level patterns
API / Semantics
libzmq

30. Philosophy
High-level patterns
API / Semantics
libzmq

31. What do we want?

32. What do we want?
• Near feature/semantic parity with ZeroMQ

33. What do we want?
• Near feature/semantic parity with ZeroMQ
• Throughput performance not as important

34. What do we want?
• Near feature/semantic parity with ZeroMQ
• Throughput performance not as important
• Embrace nature of the web in design

35. What do we want?
• Near feature/semantic parity with ZeroMQ
• Throughput performance not as important
• Embrace nature of the web in design
• Single connection, service multiplexing

36. What do we want?
• Near feature/semantic parity with ZeroMQ
• Throughput performance not as important
• Embrace nature of the web in design
• Single connection, service multiplexing
• Use existing transports, protocols, etc

37. NullMQ
What do we want?
• Near feature/semantic parity with ZeroMQ
• Throughput performance not as important
• Embrace nature of the web in design
• Single connection, service multiplexing
• Use existing transports, protocols, etc

38. What do we have?

39. WebSocket

40. WebSocket
• ZMTP over WebSocket?

41. WebSocket
• ZMTP over WebSocket?
• Connection inefficient

42. WebSocket
• ZMTP over WebSocket?
• Connection inefficient
• Not extensible

43. WebSocket
• ZMTP over WebSocket?
• Connection inefficient
• Not extensible
• No easy parsers

44. WebSocket

45. WebSocket
• STOMP over WebSocket?

46. WebSocket
• STOMP over WebSocket?
• Existing parsers, easy to write

47. WebSocket
• STOMP over WebSocket?
• Existing parsers, easy to write
• Very much like HTTP

48. WebSocket
• STOMP over WebSocket?
• Existing parsers, easy to write
• Very much like HTTP
• Used primarily to multiplex

49. NullMQ

50. var url = "ws://hostname/gateway";
var ctx = new nullmq.Context(url);
socket = ctx.socket(nullmq.REP);
socket.bind("nullmq://echo");
socket.recvall(function(request) {
socket.send("Got: "+request);
});

51. var url = "ws://hostname/gateway";
var ctx = new nullmq.Context(url);
socket = ctx.socket(nullmq.REQ);
socket.connect("nullmq://echo");
socket.send("Hello world!");
socket.recv(function(reply) {
console.log(reply);
// "Got: Hello world!"
});

52. Browser Server
Application Application
NullMQ NullMQ
STOMP STOMP
WebSocket WebSocket

53. Browser Gateway Backend
Application Bridge ZMQ Socket
NullMQ NullMQ ZMQ Socket
STOMP STOMP ZMQ Socket
WebSocket WebSocket

54. Presence Demo

55. NullMQ
http://github.com/progrium/nullmq
http://groups.google.com/group/nullmq
@progrium
@avalanche123

57. STOMP

58. STOMP
• Simple and human-readable like HTTP

59. STOMP
• Simple and human-readable like HTTP
• Extensible via headers

60. STOMP
• Simple and human-readable like HTTP
• Extensible via headers
• Library and server support

61. STOMP
• Simple and human-readable like HTTP
• Extensible via headers
• Library and server support
• An easy WebSocket subprotocol

62. STOMP
• Simple and human-readable like HTTP
• Extensible via headers
• Library and server support
• An easy WebSocket subprotocol
• Can be used to model “virtual connections”

63. STOMP
• Simple and human-readable like HTTP
• Extensible via headers
• Library and server support
• An easy WebSocket subprotocol
• Can be used to model “virtual connections”
• Transactions for multipart messages

64. STOMP “Extensions”
1. Frames include socket type header
2. Header for “connect” or “bind” in SUBSCRIBE
3. Req-Rep messages use “reply-to” header