• WebSocket Bonus - Chat Server And Client

    WebSockets are technology ideal for real-time tasks - such as a chat room (we all used to know them in the 90s before Facebook). I learnt how to work with the API by building a sample chat, using NodeJS for both client and server-side code. I’d like to share the result with you and a few last notes in this bonus article.

  • TDD of NodeJS WebSocket Server Using Grunt, Mocha, Sinon, Chai, and Rewire

    The title sounds like a pretty long sequence of swear words, doesn’t it? I thought it might be best to say directly what we’ll be dealing with here. Most WebSockets tutorials explain how to make things work. But no matter how hard I searched, I couldn’t find a suitable source explaining how to tackle test driven development when working with this API. In this article, I’d like to share my journey of learning WebSockets while sticking to TDD with you.

  • WebSocket NodeJS Server

    After building a sample client that was communicating with the test echo server, we can extend our knowledge of WebSockets by creating our own NodeJS server.

  • WebSocket Client - Part II

    After extending WebSocket API with our own implementation in Part I, Part II will focus on user interaction with the socket. We’ll do more html and css and jquery so it should be a little bit of a break after the javascript marathon of Part I.

  • WebSocket Client - Part I

    In the previous article, I’ve summed up why I think WebSockets are definitely worth a try. Let’s carry on with building our own client by adding functionality to the WebSocket API step by step so that we can create an abstraction layer between the server and the client. That’s what we’ll do in Part I of this article; in Part II, we’ll write the client javascript and some UI so that we can see our script in action.

  • W3C WebSocket API

    When using GitHub, you’ve probably noticed that it is very quick to show you notifications and new commits, practically real time. Quite a few web apps are now updating their data and showing notifications instantaneously. For most part, it isn’t done by polling the server every second or so, or using black magic; instead, they are using WebSockets. GitHub was my original inspiration to try WebSockets out - they seemed to be pushing web to a truly 2.0 version that can seamlessly handle and display any user interaction with the content.