How to build a message delivery status in JavaScript

When building realtime applications, we often want to know the actual time when a process or event occurs. For example, in an instant messaging application we want to know if and when our message was delivered to the intended client. We see this in WhatsApp where messages are sent in realtime and you see status of each message when it is delivered and read, with double grey tick when delivered and double blue tick when read. We can easily build a message delivery status using Pusher and JavaScript. How? Pusher has a concept of channels and event which are fundamental to it. We can send a message to a client through a channel and have that client notify us of a read receipt by triggering an event which the sender will listen to and react accordingly. Channels provide a way of filtering data and controlling access to different streams of information, while events are the primary method of packaging messages in the Pusher system which forms the basis of all communication. To implement a message delivery status with Pusher, we’ll have to subscribe to a channel and listen for events on the channel. We’ll build a simple chat application in JavaScript that will send out messages to a client and the client will trigger an event when received. Application setup To use Pusher API we have to signup and create a Pusher app from the dashboard. We can create as many applications as we want and each one will get an application id and secret key which we’ll use to initialise a Pusher instance on client or server side code. Create a new Pusher account to Pusher, or login if you already have an account. Sign Up After signup we get to the dashboard and shown a screen to setup up a new pusher app. Enter a name for the application. In this case I’ll call it “chat”. Select a cluster Select the option “Create app for multiple environments” if you want to have different instances for development, staging and production Choose a front-end tech. I’ll choose VanillaJS since I won’t be using any framework Select NodeJS as my back-end Click to create the Pusher app. Create App Code We will use channels as a means to send messages and trigger events through the channel. There are 3 types of channels in Pusher: which can be subscribed to by anyone who knows the name of the channel. Public Channel which lets your server control access to the data you are broadcasting. Private Channel which is an extension of the private channel, but forces channel subscribers to register user information when subscribing. It also enables users to know who is online. Presence Channel Clients needs to be authenticated to use the private and presence channels. For the sample app, we’ll build the client using vanilla JS and server (for authentication) using NodeJS. Because I don’t want message to go through the server, but from client to client, and I don’t need to know if the user is online or away, I’ll use a private channel for this demonstration, but the same technique will apply using any channel type. Client events can only be triggered in private or presence channels, and to use any of these channel types, the user/client must be authenticated, therefore the need for NodeJS back-end for authentication. Also, to use client events, they must be enabled for the application. Go to your Pusher dashboard and on the tab, select “Enable Client Event” and update. App Settings Back-End Since we’re building our backend in Node using Express, let’s initialise a new node app and install the needed dependencies. Run the following command: and select the default options npm init to install express and the Pusher node package npm i --save body-parser express pusher Add a new file called which will contain logic to authenticate the Pusher client and also render the static files we’ll be adding later. This file will contain the content below server.js var express = require('express');var bodyParser = require('body-parser');

var Pusher = require('pusher');

var app = express();app.use(bodyParser.json());app.use(bodyParser.urlencoded({ extended: false }));

var pusher = new Pusher({ appId: APP_ID, key: APP_KEY, secret: APP_SECRET, cluster: APP_Cluster });

app.get('/',function(req,res){ res.sendFile('index.html', {root: __dirname });});

app.use(express.static(__dirname + '/'));

app.post('/pusher/auth', function(req, res) { var socketId = req.body.socket_id; var channel = req.body.channel_name; var auth = pusher.authenticate(socketId, channel); res.send(auth);});

Comments Refresh Available Busy Away Sign Out

Send

style.css @import url("http://netdna.bootstrapcdn.com/font-awesome/4.0.3/css/font-awesome.css");.chat{ list-style: none; margin: 0; padding: 0;}

.chat li{ margin-bottom: 10px; padding-bottom: 5px; border-bottom: 1px dotted #B3A9A9;}

.chat li.left .chat-body{ margin-left: 60px;}

.chat li.right .chat-body{ margin-right: 60px;}

.chat li .chat-body p{ margin: 0; color: #777777;}

.panel .slidedown .glyphicon, .chat .glyphicon{ margin-right: 5px;}

.body-panel{ overflow-y: scroll; height: 250px;}

::-webkit-scrollbar-track{ -webkit-box-shadow: inset 0 0 6px rgba(0,0,0,0.3); background-color: #F5F5F5;}

::-webkit-scrollbar{ width: 12px; background-color: #F5F5F5;}

::-webkit-scrollbar-thumb{ -webkit-box-shadow: inset 0 0 6px rgba(0,0,0,.3); background-color: #555;} The page we added holds a 1-to-1 chat template. At line we added script to load the Pusher JavaScript library, and at we’re loading a custom JavaScript file which we will use to handle interactions from the page. Add this file with the following content: 18 19 index.js $(document).ready(function(){ // Enable pusher logging - don't include this in production Pusher.logToConsole = true;

var pusher = new Pusher('APP_KEY', { cluster: 'eu', encrypted: false });

var channel = pusher.subscribe('private-channel'); //channel name prefixed with 'private' because it'll be a private channel}); From the code above we first connect to Pusher by creating a Pusher object with the and cluster. These values are gotten from the Pusher dashboard. is set to false to allow it to send information on an unencrypted connection. App_Key encrypted Afterwards, we subscribe to a channel which is to be used for sending out messages. Channel names can be anything, but must be a maximum of 164 characters. Another restriction on a private channel is that it must be prefixed with . private- Next we bind to events. This way we can receive messages from a client through the channel we subscribed to. Add the following line to index.js channel.bind('client-message-added', onMessageAdded);channel.bind('client-message-delivered', onMessageDelivered);

$('#btn-chat').click(function(){ const id = generateId(); const message = $("#message").val(); $("#message").val("");

let template = $("#new-message-me").html(); template = template.replace("{{id}}", id); template = template.replace("{{body}}", message); template = template.replace("{{status}}", "");

$(".chat").append(template);

//send message channel.trigger("client-message-added", { id, message });});function generateId() { return Math.round(new Date().getTime() + (Math.random() * 100));}

function onMessageAdded(data) { let template = $("#new-message-other").html(); template = template.replace("{{body}}", data.message);

$(".chat").append(template);

//notify sender channel.trigger("client-message-delivered", { id: data.id });}

function onMessageDelivered(data) { $("#" + data.id).find("small").html("Delivered");} I will be triggering events from the client and don’t want it to go through the back-end or be validated. This is just for this demo. must be prefixed by that is why I have done so with the code above. Events with any other prefix will be rejected by the Pusher server, as will events sent to channels to which the client is not subscribed. Client events client- It is important that you apply additional care when triggering client events. Since these originate from other users, and could be subject to tampering by a malicious user of your site. will be triggered when a user enters a new message. Once the other user gets the message, it is displayed on the page, and event is triggered to notify the sender of receipt. This way we can achieve the objective of getting notified about message delivery status in our application. client-message-added client-message-delivered Run the application and see how it works. Wrap Up With what you’ve seen so far, and knowing that Channels and Events are the fundamentals of Pusher, I hope I’ve shown you how to implement a message delivery status using Pusher and JavaScript. You can find the code on GitHub This was originally published on Pusher