I have been working with WebSockets since their release. While I like the idea of a browser based full duplex communication between the client and server, one of my favorite interests with WebSockets has been getting multiple browser based apps to communicate with each other in realtime.
In this article, I will give an example for a realtime application where users can collaborate on a shared html5 canvas using a jQuery plugin I wrote a few years back. I will be using Swift on the server side with the web framework Vapor.
For more information about the plugin that I developed, you can review an article that I wrote for it here.
Requirements
You will of course need to have Swift 3.x and Vapor installed on your local machine and if you haven’t already done this, there is a great step by step tutorial you can follow here.
Don’t stop here If you think Swift is only for Apple OSs because it can actually be run on multiple OSs and the above instructions will given you an example of setting it up to run on Ubuntu. I wrote this article demonstrating how to setup a Virtual Ubuntu machine for Vapor.
Finally, the rest of this post assumes you already have a basic understanding of HTML, Javascript, Swift and Vapor. For those wanting to learn more about Vapor, there are some great how to videos and articles to get started here.
Setting up Client
I don’t plan to cover the details of laying out the page but for a quick demonstration of what everything will look like, you can go here.
Talking with Server
To make communications between the clients simple, I will be using JSON objects.
The following code will be used to store and manage the WebSocket communications that are sent and received:
function dooScribConnection(host) {
var scrib = this;
scrib.ws = new WebSocket('wss://' + host);
scrib.ws.onopen = function() {
var connRequest =
JSON.stringify({'command': 'connect', 'username': id})
scrib.ws.send(connRequest)
};
scrib.ws.onmessage = function(event) {
var msg = JSON.parse(event.data);
if (msg.command == "click") {
prevPoint[msg.username] = msg;
} else if (msg.command == "paint") {
surface.drawLine(prevPoint[msg.username].X,
prevPoint[msg.username].Y, msg.X, msg.Y, msg.color, msg.pen);
prevPoint[msg.username] = msg;
} else if (msg.command == "clear") {
surface.clearSurface();
}
};
scrib.send = function(event) {
scrib.ws.send(event);
};
};
The connection to the server is established as soon as the WebSocket object is created. The onOpen function is called once that connection is established. By making a call to send information to the server here, it will allow the server to store instance information about each of its connections. To make sure that each user is uniquely identified, the id var is established using the following:
var id = Math.round($.now()*Math.random());
For messaging to the server, I added the send function which will send the JSON objects that are passed as a parameter to it.
Whenever a message is received, the onmessage function is called and from there, you can switch on the command type (added to the JSON message) and take the appropriate action. Currently, the following commands (JSON objects) are of interest for handling inside the browser:
click – This is used to establish the starting point for when the user has started drawing.paint – This is used to draw a line from the previous point to the current one.clear – A command that allows users to clear the drawing canvas.
Setting up Canvas (DooScrib Plugin)
The following code is for setting up the jquery plugin as soon as the page has been loaded and is ready:
$(document).ready(function(){
var height = $('#raw() { #surface }').height();
var width = $('#raw() { #surface }').width();
dooscrib = new dooScribConnection(window.location.host + "/dooscrib");
surface = new $('#raw() { #surface }').dooScribPlugin({
width:width,
height:400,
cssClass:'pad',
penSize:4,
onMove:function(e) {
var msg = JSON.stringify({'command': 'mousemove',
'username': id, 'X': e.X, 'Y': e.Y });
dooscrib.send(msg);
},
onClick:function(e) {
var msg = JSON.stringify({'command': 'click',
'username': id, 'X': e.X, 'Y': e.Y});
dooscrib.send(msg);
},
onPaint:function(e) {
var msg = JSON.stringify({'command': 'paint',
'username': id, 'X': e.X, 'Y': e.Y,'pen':
surface.penSize(),'color':surface.lineColor()});
dooscrib.send(msg);
},
onRelease:function(e) {
var msg = JSON.stringify({'command': 'release',
'username': id, 'X': e.X, 'Y': e.Y});
dooscrib.send(msg);
}
});
});
The drawing for the current surface is handled by the plugin which then messages everything that it is being done. With each message, there is a JSON message created which is then sent to the server which will redirect to all the other users.
Setting Up Server
For the server implementation, I created the following Controller object which handles all of the WebSockets communications as well as routes for the different web pages:
final class ScribController {
var dooscribs : [String: WebSocket]
var droplet : Droplet
init(drop: Droplet) {
dooscribs = [:]
droplet = drop
droplet.get("", handler: scribRequest)
droplet.get("about", handler: aboutRequest)
droplet.socket("dooscrib", handler: socketHandler )
}
func aboutRequest(request: Request) throws -> ResponseRepresentable {
return try droplet.view.make("about")
}
func scribRequest(request: Request) throws -> ResponseRepresentable {
return try droplet.view.make("socket")
}
func socketHandler(request: Request, socket: WebSocket) throws {
var scribUser: String? = nil
try background {
while socket.state == .open {
try? socket.ping()
drop.console.wait(seconds: 5)
}
}
socket.onText = { socket, message in
let json = try JSON(bytes: Array(message.utf8))
guard let msgType = json.object?["command"]?.string,
let user = json.object?["username"]?.string else {
return
}
if msgType.equals(any: "connect") {
scribUser = user
self.dooscribs[user] = socket
let response = try JSON(node: [
"command":"connected",
"username": user
])
for (_, connection) in self.dooscribs {
try connection.send(response)
}
} else if (msgType.equals(any: "clear")) {
for (_, connection) in self.dooscribs {
try connection.send(json)
}
} else {
for (scrib, connection) in self.dooscribs {
if (!scrib.equals(any: user)) {
try connection.send(json)
}
}
}
}
socket.onClose = { ws, _, _, _ in
guard let user = scribUser else {
return
}
let disconn = try JSON(node: [
"command": "disconnect",
"username": user
])
for (remote, connection) in self.dooscribs {
if (!remote.equals(any: user)) {
try connection.send(disconn)
}
}
self.dooscribs.removeValue(forKey: user)
}
}
}
I won’t be covering the get route handlers that are established in the controller with any great detail. From the code however, you can see that they are sending back the pages the user requested.
Sending JSON Messages
Much to my surprise, the WebSocket class does not have a function for sending JSON packets so I created the following extension to handle that:
extension WebSocket {
func send(_ json: JSON) throws {
let data = try json.makeBytes()
try send(data.string)
}
}
Handling Messages
Messages are handled via the onText <span class="s1">EventHandler</span> which is called with a WebSocket and String passed in via closure. The string data is parsed into a JSON object so that command and user id that should be sent with each message.
For the connect message, the user id and accompanying WebSocket are saved in the dooscribs dictionary and then a connected message is created and, much like the clear message, it gets sent to all of the connections.
The other messages that are received get forwarded to all of the current connections with an exception for the one where the message is.
Handling Connections and Users
Each connection will be stored in the dooscribs dictionary which is a pairing of the unique id that was generated by the browser and the WebSocket for their connection.
Whenever a connection is closed (user leaves page, closes browser), the onClose handler is called informing of the event. For cleanup purposes, send a disconnect message to all of the clients that are stored in the dooScribs dictionary, minus the connection that just closed, as well as remove that user from the dictionary.
Issues – Random Disconnection
Something I noticed in my development was that clients were disconnecting for what seemed at the time as unknown reasons. After some research, I found that “quiet” connections will automatically get disconnected. To handle this, I created the background handler so that it would ping the socket every 5 seconds to keep channels open.
Conclusion
Hopefully, this gives you some ideas for processing realtime data in your applications. In the future, I plan to expand the dooScrib application so that it can handle different rooms as well as text based messaging. The code for the dooScrib plugin as well a Node.js Implementation and this Vapor implementation can be found here.
For now, enjoy and as always, happy coding!!!
