npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

madlib-ws-client

v0.1.8

Published

Platform agnostic WebSocket client implementation

Downloads

7

Readme

madlib-ws-client

Build Status NPM version Built with Grunt

Npm Downloads

Platform agnostic WebSocket client implementation

philosophy

JavaScript is the language of the web. Wouldn't it be nice if we could stop having to rewrite (most) of our code for all those web connected platforms running on JavaScript? That is what madLib hopes to achieve. The focus of madLib is to have the same old boring stuff ready made for multiple platforms. Write your core application logic once using modules and never worry about the basics stuff again. Basics including XHR, XML, JSON, host mappings, settings, storage, etcetera. The idea is to use the tried and proven frameworks where available and use madlib based modules as the missing link.

Currently madLib is focused on supporting the following platforms:

  • Web browsers (IE6+, Chrome, Firefox, Opera)
  • Appcelerator/Titanium
  • PhoneGap
  • NodeJS

The NodeJS implementation uses the ws module:

For Titanium I'm relying on TiWS:

installation

$ npm install madlib-ws-client --save

If you are using this in a titaniumifier (https://github.com/smclab/titaniumifier) project you will need to add a native dependency to the TiWS module in your package.json like so:

  "nativeDependencies": {
    "net.iamyellow.tiws": "0.1.2"
  },

Change the version number as required

usage

The WebSocket client is a very thin wrapper around the browsers native WebSocket support. This module does not polyfill WebSocket support for older browsers (IE8/9).

I wrote this module to hide which platform needed a WebSocket client. My specific need at the time was to write a client API module that would work with both Node.JS and an Appcelerator App.

To not have to mess around with event emitting and listening differences I decided to rely on callbacks for the websocket events. Below is an example to call the websocket echo server using this module.

var WebSocket = require( "madlib-ws-client" );
var client    = new WebSocket( "ws://echo.websocket.org/?encoding=text" );
testString    = "Hello world!";

// Setup callbacks
//
client.onOpen = function()
{
    // Once a connection is established we can send the echo test
    //
    client.send( testString );
};

client.onMessage = function( response )
{
    console.log( "Got echo response", response )
};

// Connect to the echo server
//
client.connect();