WarsawJS Presentation Template

What are we looking at?

• Super boring examples
• Cool features!
• Hey! How does it work?
• It's getting tight in here
• ART!

What is socket.io

• Real-time
• Bi-directional
• Event based
• Communication
• Between server and clients

Types of messages

• Text
• Binary

Transports

• Polling
  • jsonp
  • xhr
• Websocket
• Flashsocket

• http://warsawjs.4screens.net/example-bidirectional
• http://goo.gl/UAEaq1

• http://warsawjs.4screens.net/example-broadcast
• http://goo.gl/ml00Ea

Namespaces

• Each namespace emits and reacts to its own events
• Clients cannot connect to namespace if it's not "created" on the server
• You are connecting to namespace so there is no need to rejon after reconnect
• Each connection is namespaced (default namespace is "/")

Rooms

• You can join/leave room AFTER you are connected
• Think about it as filters for received messages
• You can join many rooms at once
• You need to rejoin rooms after every reconnect
• A little "room" is created for every user (with his ID as name)

Not all messages are created equal - Volatile Messages

• If it wont hurt you application if some of the messages are dropped
• When are messages dropped?
  • When network is slow
  • When application is slow
  • When transport is polling and is in the middle of reconnecting

Transport upgrading

1. polling
2. probing
3. upgrading

What happens when you suddenly get successful?

Adapter - Anything with pub-sub works

• Redis
• ZeroMQ
• ...
• Profit?

Emitter

Emit messages from outside of node/socket thread like a boss

• http://warsawjs.4screens.net/example-ball
• http://goo.gl/7R8Wne

• http://warsawjs.4screens.net/example-dots
• http://goo.gl/Z123Nn

Usefull links

• http://socket.io
• https://github.com/socketio/engine.io
• https://auth0.com/blog/2014/01/15/auth-with-socket-io/