Simple Dart + WebSocket demo

[EDIT: Updated on 2013-03-05]

I just posted a simple demo of Dart with WebSockets. Not only does it show how to connect to a WebSocket server and send messages, it also shows off a few neat features of the Dart language.

(The code follows below, or check out the full open source project.)

Look mom, no classes!

Dart is a class-based object oriented language, but that doesn't mean you are required to wrap everything in a class. No sir, this is Dart, not Java. In Dart, you can use top level functions and top level variables.

Libraries for modularity

Dart organizes code into libraries for modularity. For example, this code uses the dart:html library for the WebSocket code. Concerned about bloat here? Don't be! Thanks to tree-shaking, the code that you don't use is eliminated during a (optional) compile step. The Dart to JavaScript compiler uses tree shaking to help generate minimal JavaScript code (still more work to do here). An upcoming Dart to Dart script will also generate a minimal Dart file for your app. So include all the libraries that you want, and stop worrying about how many bytes a dependencies adds.

Inline function definitions

Dart's syntax for inline function definitions is very handy for callbacks. For example, the code for the reconnection logic reads:

new Timer(new Duration(seconds:retrySeconds),
  () => initWebSocket(url, retrySeconds));

Optional parameters with default values

Make function parameters optional by wrapping them in square brackets. In the code below, I made retrySeconds optional, with a default value of 2.

Main is where it starts

I know where every Dart program starts. This might sound minor, but understanding the structure of your program is key for building larger apps. Look for the main() function to learn where the script begins.

The code

You can also check out the full open source code for the Dart + WebSockets demo. Here's a snippet.

 * See LICENSE file.

import 'dart:html';
import 'dart:async';

WebSocket ws;

outputMsg(String msg) {
  var output = query('#output');
  output.text = "${output.text}\n${msg}";

void initWebSocket(String url, [int retrySeconds = 2]) {
  var encounteredError = false;
  outputMsg("Connecting to Web socket");
  ws = new WebSocket(url);
  ws.onOpen.listen((e) {
    ws.send('Hello from Dart!');
  ws.onClose.listen((e) {
    outputMsg('web socket closed, retrying in $retrySeconds seconds');
    if (!encounteredError) {
      new Timer(new Duration(seconds:retrySeconds),
          () => initWebSocket(url, retrySeconds*2));
    encounteredError = true;
  ws.onError.listen((e) {
    outputMsg("Error connecting to ws");
    if (!encounteredError) {
      new Timer(new Duration(seconds:retrySeconds),
          () => initWebSocket(url, retrySeconds*2));
    encounteredError = true;
  ws.onMessage.listen((MessageEvent e) {
    outputMsg('received message ${}');

void main() {

1 comment

Popular posts from this blog

  • Sponsor:  Register today for  New Game, the conference for HTML5 game developers . Learn from Mozilla, Opera, Google, Spil, Bocoup, Mandreel, Subsonic, Gamesalad, EA, Zynga, and others at this intimate and technically rich conference. Join us for two days of content from developers building HTML5 games today. Nov 1-2, 2011 in San Francisco.  Register now ! This is the second article in a Box2D series, following the Box2D Orientation article. The Box2DWeb port of Box2D contains a nice example to show off the basics of integrating physics simulations into your web app. This post will provide a walkthrough of the example, explaining the high level concepts and code. First, let's see the example in action. The code for the above is open source and available on GitHub. It was adapted from Box2DWeb's example . Animating Before we look at Box2D, it's important to understand how the above simulation is animated. You might think setInterval or setTimeout is
  • In which I port a snazzy little JavaScript audio web app to Dart , discover a bug, and high-five type annotations. Here's what I learned. [As it says in the header of this blog, I'm a seasoned Dart developer. However, I certainly don't write Dart every day (I wish!). Don't interpret this post as "Hi, I'm new to Dart". Instead, interpret this post as "I'm applying what I've been documenting."] This post analyzes two versions of the same app, both the original (JavaScript) version and the Dart version. The original version is a proxy for any small JavaScript app, there's nothing particularly special about the original version, which is why it made for a good example. This post discusses the differences between the two implementations: file organization, dependencies and modules, shims, classes, type annotations, event handling, calling multiple methods, asynchronous programming, animation, and interop with JavaScript libraries. F
  • Angular and Polymer, sitting in a DOM tree, B-i-n-d-i-n-g. First comes components, Then comes elements, Then comes the interop with the node dot bind. Angular , a super heroic MVC framework, and Polymer , polyfills and enhancements for custom elements built on top of Web Components, can live harmoniously in the same app. This post shows you how to connect Angular-controlled components to Polymer-controlled elements via data binding. And we do it all in Dart . Angular and Polymer I get asked "Should I use Angular or Polymer?" a lot. My answer is, "Yes". That is, both libraries have distinct strengths, and you can use both in the same app. Polymer excels at creating encapsulated custom elements. You can use those custom elements in any web app or web page, regardless if that app is built with Angular, Ember, etc. Angular excels at application engineering, with dependency injection, end-to-end testability, routing, and services. Here are som