pusher-js 8.4.0 → 8.4.3

package/src/runtimes/web/dom/sockjs/README.md

@@ -1,388 +0,0 @@
-SockJS family:
-
-  * [SockJS-client](https://github.com/sockjs/sockjs-client) JavaScript client library
-  * [SockJS-node](https://github.com/sockjs/sockjs-node) Node.js server
-  * [SockJS-erlang](https://github.com/sockjs/sockjs-erlang) Erlang server
-  * [SockJS-lua](https://github.com/luvit/sockjs-luvit) Lua/Luvit server
-  * [SockJS-tornado](https://github.com/MrJoes/sockjs-tornado) Python/Tornado server
-  * [vert.x](https://github.com/vert-x/vert.x) Java/vert.x server
-
-Work in progress:
-
-  * [SockJS-ruby](https://github.com/sockjs/sockjs-ruby)
-  * [SockJS-netty](https://github.com/cgbystrom/sockjs-netty)
-  * [SockJS-gevent](https://github.com/sdiehl/sockjs-gevent) ([SockJS-gevent fork](https://github.com/njoyce/sockjs-gevent))
-  * [pyramid-SockJS](https://github.com/fafhrd91/pyramid_sockjs)
-  * [wildcloud-websockets](https://github.com/wildcloud/wildcloud-websockets)
-  * [SockJS-cyclone](https://github.com/flaviogrossi/sockjs-cyclone)
-  * [SockJS-twisted](https://github.com/Fugiman/sockjs-twisted/)
-  * [wai-SockJS](https://github.com/Palmik/wai-sockjs)
-  * [SockJS-perl](https://github.com/vti/sockjs-perl)
-
-
-SockJS-client
-=============
-
-SockJS is a browser JavaScript library that provides a WebSocket-like
-object. SockJS gives you a coherent, cross-browser, Javascript API
-which creates a low latency, full duplex, cross-domain communication
-channel between the browser and the web server.
-
-Under the hood SockJS tries to use native WebSockets first. If that
-fails it can use a variety of browser-specific transport protocols and
-presents them through WebSocket-like abstractions.
-
-SockJS is intended to work for all modern browsers and in environments
-which don't support WebSocket protcol, for example behind restrictive
-corporate proxies.
-
-SockJS-client does require a server counterpart:
-
- * [SockJS-node](https://github.com/sockjs/sockjs-node) is a SockJS
-   server for Node.js.
-
-
-Philosophy:
-
- * The API should follow
-   [HTML5 Websockets API](http://dev.w3.org/html5/websockets/) as
-   closely as possible.
- * All the transports must support cross domain connections out of the
-   box. It's possible and recommended to host SockJS server on
-   different server than your main web site.
- * There is a support for at least one streaming protocol for every
-   major browser.
- * Streaming transports should work cross-domain and
-   should support cookies (for cookie-based sticky sessions).
- * Polling transports are be used as a fallback for old browsers and
-   hosts behind restrictive proxies.
- * Connection establishment should be fast and lightweight.
- * No Flash inside (no need to open port 843 - which doesn't work
-   through proxies, no need to host 'crossdomain.xml', no need
-   [to wait for 3 seconds](https://github.com/gimite/web-socket-js/issues/49)
-   in order to detect problems)
-
-
-Subscribe to
-[SockJS mailing list](https://groups.google.com/forum/#!forum/sockjs) for
-discussions and support.
-
-
-Live QUnit tests and smoke tests
---------------------------------
-
-SockJS comes with some QUnit tests and a few smoke tests (using
-[SockJS-node](https://github.com/sockjs/sockjs-client) on the server
-side). At the moment they are deployed in few places:
-
- * http://sockjs.popcnt.org/ and https://sockjs.popcnt.org/ (hosted in Europe)
- * http://sockjs.cloudfoundry.com/ (CloudFoundry, websockets disabled, loadbalanced)
- * https://sockjs.cloudfoundry.com/ (CloudFoundry SSL, websockets disabled, loadbalanced)
-
-
-Example
--------
-
-SockJS mimics [WebSockets API](http://dev.w3.org/html5/websockets/)
-but instead of `WebSocket` there is a `SockJS` Javascript object.
-
-First, you need to load SockJS JavaScript library, for example you can
-put that in your http head:
-
-    <script src="http://cdn.sockjs.org/sockjs-0.3.min.js">
-      </script>
-
-After the script is loaded you can establish a connection with the
-SockJS server. Here's a simple example:
-
-```javascript
-<script>
-   var sock = new SockJS('http://mydomain.com/my_prefix');
-   sock.onopen = function() {
-       console.log('open');
-   };
-   sock.onmessage = function(e) {
-       console.log('message', e.data);
-   };
-   sock.onclose = function() {
-       console.log('close');
-   };
-</script>
-```
-
-SockJS-client API
------------------
-
-### SockJS class
-
-Similar to 'WebSocket' class 'SockJS' constructor takes one, or more arguments:
-
-```javascript
-var sockjs = new SockJS(url, _reserved, options);
-```
-
-Where `options` is a hash which can contain:
-
- *  **debug (boolean)**
-
-    Print some debugging messages using 'console.log'.
-
- *  **devel (boolean)**
-
-    Development mode. Currently setting it disables caching of the
-    'iframe.html'.
-
- *  **protocols_whitelist (list of strings)**
-
-    Sometimes it is useful to disable some fallback protocols. This
-    option allows you to supply a list protocols that may be used by
-    SockJS. By default all available protocols will be used, which is
-    equivalent to supplying: "['websocket', 'xdr-streaming', 'xhr-streaming',
-    'iframe-eventsource', 'iframe-htmlfile', 'xdr-polling', 'xhr-polling',
-    'iframe-xhr-polling', 'jsonp-polling']"
-
-
-Although the 'SockJS' object tries to emulate the 'WebSocket'
-behaviour, it's impossible to support all features. One of the
-important SockJS limitations is the fact that you're not allowed to
-open more than one SockJS connection to a single domain at a time.
-This limitation is caused by a in-browser limit of outgoing
-connections - usually [browsers don't allow opening more than two
-outgoing connections to a single domain](http://stackoverflow.com/questions/985431/max-parallel-http-connections-in-a-browser). Single SockJS session
-requires those two connections - one for downloading data, other for
-sending messages.  Opening second SockJS session at the same time
-would most probably block and can result in both sessions timing out.
-
-Opening more than one SockJS connection at a time is generally a
-bad practice. If you absolutely must do it, you can use
-mutliple subdomains, using different subdomain for every
-SockJS connection.
-
-Supported transports, by browser (html served from http:// or https://)
------------------------------------------------------------------------
-
-_Browser_       | _Websockets_     | _Streaming_ | _Polling_
-----------------|------------------|-------------|-------------------
-IE 6, 7         | no               | no          | jsonp-polling
-IE 8, 9 (cookies=no) |    no       | xdr-streaming &dagger; | xdr-polling &dagger;
-IE 8, 9 (cookies=yes)|    no       | iframe-htmlfile | iframe-xhr-polling
-IE 10           | rfc6455          | xhr-streaming   | xhr-polling
-Chrome 6-13     | hixie-76         | xhr-streaming   | xhr-polling
-Chrome 14+      | hybi-10 / rfc6455| xhr-streaming   | xhr-polling
-Firefox <10     | no &Dagger;      | xhr-streaming   | xhr-polling
-Firefox 10+     | hybi-10 / rfc6455| xhr-streaming   | xhr-polling
-Safari 5        | hixie-76         | xhr-streaming   | xhr-polling
-Opera 10.70+    | no &Dagger;      | iframe-eventsource | iframe-xhr-polling
-Konqueror       | no               | no          | jsonp-polling
-
-
- * **&dagger;**: IE 8+ supports [XDomainRequest][^9], which is
-    esentially a modified AJAX/XHR that can do requests across
-    domains. But unfortunately it doesn't send any cookies, which
-    makes it inaproppriate for deployments when the load balancer uses
-    JSESSIONID cookie to do sticky sessions.
-
- * **&Dagger;**: Firefox 4.0 and Opera 11.00 and shipped with disabled
-     Websockets "hixie-76". They can still be enabled by manually
-     changing a browser setting.
-
-Supported transports, by browser (html served from file://)
------------------------------------------------------------
-
-Sometimes you may want to serve your html from "file://" address - for
-development or if you're using PhoneGap or similar technologies. But
-due to the Cross Origin Policy files served from "file://" have no
-Origin, and that means some of SockJS transports won't work. For this
-reason the SockJS protocol table is different than usually, major
-differences are:
-
-_Browser_       | _Websockets_  | _Streaming_        | _Polling_
-----------------|---------------|--------------------|-------------------
-IE 8, 9         | same as above | iframe-htmlfile    | iframe-xhr-polling
-Other           | same as above | iframe-eventsource | iframe-xhr-polling
-
-Supported transports, by name
------------------------------
-
-_Transport_          | _References_
----------------------|---------------
-websocket (rfc6455)  | [rfc 6455][^10]
-websocket (hixie-76) | [draft-hixie-thewebsocketprotocol-76][^1]
-websocket (hybi-10)  | [draft-ietf-hybi-thewebsocketprotocol-10][^2]
-xhr-streaming        | Transport using [Cross domain XHR][^5] [streaming][^7] capability (readyState=3).
-xdr-streaming        | Transport using [XDomainRequest][^9] [streaming][^7] capability (readyState=3).
-iframe-eventsource   | [EventSource][^4] used from an [iframe via postMessage][^3].
-iframe-htmlfile      | [HtmlFile][^8] used from an [iframe via postMessage][^3].
-xhr-polling          | Long-polling using [cross domain XHR][^5].
-xdr-polling          | Long-polling using [XDomainRequest][^9].
-iframe-xhr-polling   | Long-polling using normal AJAX from an [iframe via postMessage][^3].
-jsonp-polling        | Slow and old fashioned [JSONP polling][^6]. This transport will show "busy indicator" (aka: "spinning wheel") when sending data.
-
-
-[^1]: http://tools.ietf.org/html/draft-hixie-thewebsocketprotocol-76
-[^2]: http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-10
-[^3]: https://developer.mozilla.org/en/DOM/window.postMessage
-[^4]: http://dev.w3.org/html5/eventsource/
-[^5]: https://secure.wikimedia.org/wikipedia/en/wiki/XMLHttpRequest#Cross-domain_requests
-[^6]: https://secure.wikimedia.org/wikipedia/en/wiki/JSONP
-[^7]: http://www.debugtheweb.com/test/teststreaming.aspx
-[^8]: http://cometdaily.com/2007/11/18/ie-activexhtmlfile-transport-part-ii/
-[^9]: http://blogs.msdn.com/b/ieinternals/archive/2010/05/13/xdomainrequest-restrictions-limitations-and-workarounds.aspx
-[^10]: http://www.rfc-editor.org/rfc/rfc6455.txt
-
-
-Connecting to SockJS without the client
----------------------------------------
-
-Although the main point of SockJS it to enable browser-to-server
-connectivity, it is possible to connect to SockJS from an external
-application. Any SockJS server complying with 0.3 protocol does
-support a raw WebSocket url. The raw WebSocket url for the test server
-looks like:
-
- * ws://localhost:8081/echo/websocket
-
-You can connect any WebSocket RFC 6455 compliant WebSocket client to
-this url. This can be a command line client, external application,
-third party code or even a browser (though I don't know why you would
-want to do so).
-
-
-Deployment
-----------
-
-In order to utilize best performance you should use the SockJS-client
-releases hosted on SockJS CDN. You should use a version of sockjs-client
-that supports the protocol used by your server. For example:
-
-    <script src="http://cdn.sockjs.org/sockjs-0.3.min.js">
-      </script>
-
-A list of files hosted on a CDN is available here: http://sockjs.github.com/sockjs-client/ .
-
-You can also use or CDN via https (using Cloud Front domain name):
-
-    <script src="https://d1fxtkz8shb9d2.cloudfront.net/sockjs-0.3.js">
-      </script>
-
-For server-side deployment tricks, especially about load balancing and
-session stickiness, take a look at the
-[SockJS-node readme](https://github.com/sockjs/sockjs-node#readme).
-
-
-Development and testing
------------------------
-
-SockJS-client needs [Node.js](http://nodejs.org/) for running a test
-server and JavaScript minification. If you want to work on
-SockJS-client source code, check out the git repo and follow this
-steps:
-
-    cd sockjs-client
-    npm install
-    npm install --dev
-
-To generate JavaScript run:
-
-    make sockjs.js
-
-To generate minified JavaScript run:
-
-    make sockjs.min.js
-
-(To generate both run `make build`.)
-
-
-### Testing
-
-Once you compiled SockJS-client you may want to check if your changes
-pass all the tests. To run the tests you need a server that can answer
-various SockJS requests. A common way is to use `SockJS-node` test
-server for that. To run it (by default it will be listening on port 8081):
-
-    cd sockjs-node
-    npm install
-    npm install --dev
-    make build
-    make test_server
-
-At this point you're ready to run a SockJS-client server that will
-server your freshly compiled JavaScript and various static http and
-javscript files (by default it will run on port 8080).
-
-    cd sockjs-client
-    make test
-
-At that point you should have two web servers running: sockjs-node on
-8081 and sockjs-client on 8080. When you open the browser on
-[http://localhost:8080/](http://localhost:8080/) you should be able
-run the QUnit tests against your sockjs-node server.
-
-If you look at your browser console you will see warnings like that:
-
-    Incompatibile SockJS! Main site uses: "a", the iframe: "b".
-
-This is due to a fact that SockJS-node test server is using compiled
-javascript from CDN, rather than your freshly compiled version. To fix
-that you must amend `sockjs_url` that is used by SockJS-node test
-server. Edit the [`config.js`](https://github.com/sockjs/sockjs-node/blob/master/examples/test_server/config.js) file:
-
-    vim sockjs-node/examples/test_server/config.js
-
-And replace `sockjs_url` setting which by default points to CDN:
-
-    sockjs_url: 'http://cdn.sockjs.org/sockjs-0.3.min.js',
-
-to a freshly compiled sockjs, for example:
-
-    sockjs_url: 'http://localhost:8080/lib/sockjs.js',
-
-
-Also, if you want to run tests agains SockJS server not running on
-`localhost:8081` you may want to edit the
-[`tests/config.js`](https://github.com/sockjs/sockjs-client/blob/master/tests/config.js)
-file.
-
-Additionally, if you're doing more serious development consider using
-`make serve`, which will automatically reload the server when you
-modify the source code.
-
-
-Browser Quirks
---------------
-
-There are various browser quirks which we don't intend to address:
-
- * Pressing ESC in Firefox closes SockJS connection. For a workaround
-   and discussion see [#18](https://github.com/sockjs/sockjs-client/issues/18).
- * Jsonp-polling transport will show a "spinning wheel" (aka. "busy indicator")
-   when sending data.
- * You can't open more than one SockJS connection to one domain at the
-   same time due to [the browsers limit of consurrent connections](http://stackoverflow.com/questions/985431/max-parallel-http-connections-in-a-browser)
-   (this limit is not counting native websockets connections).
- * Although SockJS is trying to escape any strange Unicode characters
-   (even invalid ones - [like surrogates \xD800-\xDBFF](http://en.wikipedia.org/wiki/Mapping_of_Unicode_characters#Surrogates) or [\xFFFE and \xFFFF](https://en.wikipedia.org/wiki/Unicode#Character_General_Category))
-   it's advisable to use only valid characters. Using invalid
-   characters is a bit slower, and may not work with SockJS servers
-   that have a proper Unicode support.
- * Having a global function called `onmessage` or such is probably a
-   bad idea, as it could be called by the built-in `postMessage` API.
- * From SockJS point of view there is nothing special about
-   SSL/HTTPS. Connecting between unencrypted and encrypted sites
-   should work just fine.
- * Although SockJS does best to support both prefix and cookie based
-   sticky sessions, the latter may not work well cross-domain with
-   browsers that don't accept third-party cookies by default (Safari).
-   In order to get around this make sure you're connecting to sockjs
-   from the same parent domain as the main site. For example
-   'sockjs.a.com' is able to set cookies if you're connecting from
-   'www.a.com' or 'a.com'.
- * Trying to connect from secure "https://" to insecure "http://" is
-   not good idea. The other way around should be fine.
- * Long polling is known to cause problems on Heroku, but
-   [workaround for SockJS is available](https://github.com/sockjs/sockjs-node/issues/57#issuecomment-5242187).
- * Don't use "javascript:" links on a page that uses SockJS. For
-   some reason clickling on this type of link breaks XDR/XHR requests
-   on IE (see [#90](https://github.com/sockjs/sockjs-client/issues/90)).
- * SockJS [websocket transport is more stable over SSL](https://github.com/sockjs/sockjs-client/issues/94). If you're a serious SockJS user consider using SSL.
-   over SSL](https://github.com/sockjs/sockjs-client/issues/94).

package/src/runtimes/web/dom/sockjs/VERSION-GEN

@@ -1,17 +0,0 @@
-#!/bin/sh
-
-LF='
-'
-
-VN=$(git describe --match "v[0-9]*" --abbrev=4 HEAD 2>/dev/null)
-case "$VN" in
-    *$LF*) (exit 1) ;;
-v[0-9]*)
-        git update-index -q --refresh
-        test -z "$(git diff-index --name-only HEAD --)" ||
-        VN="$VN-dirty" ;;
-esac
-VN=$(echo "$VN" | sed -e 's/-/./g');
-VN=$(expr "$VN" : v*'\(.*\)')
-
-echo "$VN"

package/src/runtimes/web/dom/sockjs/bin/render.coffee

@@ -1,111 +0,0 @@
-#!/usr/bin/env coffee
-#
-# ***** BEGIN LICENSE BLOCK *****
-# Copyright (c) 2011-2012 VMware, Inc.
-#
-# For the license see COPYING.
-# ***** END LICENSE BLOCK *****
-
-
-fs = require('fs')
-uglify = require('uglify-js')
-optparse = require('optparse')
-
-array_flatten = (arr, acc) ->
-    if typeof acc is 'undefined'
-        acc = []
-    if typeof arr is 'string'
-        acc.push(arr)
-        return acc
-
-    if arr.constructor isnt Array
-        throw "Value is not an Array nor a String!"
-
-    for v in arr
-        if typeof v is 'string'
-            acc.push(v)
-        else if v.constructor is Array
-            array_flatten(v, acc)
-        else
-            throw "Value is not an Array nor a String!"
-    return acc
-
-stringify_unicode = (str) ->
-    str = str.replace /[\u0100-\uffff]/g, (ch) ->
-            return "\\u" + ('0000' + ch.charCodeAt(0).toString(16)).substr(-4)
-    str = str.replace /[\x00-\x08\x0b-\x1f\x7f-\xff]/g, (ch) ->
-            return "\\x" + ('00' + ch.charCodeAt(0).toString(16)).substr(-2)
-    return str
-
-
-minify = (data, minify_options)->
-    ast = uglify.parser.parse(data)
-    ast = uglify.uglify.ast_mangle(ast, minify_options)
-    ast = uglify.uglify.ast_squeeze(ast)
-    uglify.uglify.gen_code(ast, minify_options)
-
-render = (filename, depth, options) ->
-    tags =
-        include: (args) ->
-            if (args.length > 1 and args[1].indexOf('c') isnt -1 and
-                     options.minify is false)
-                options.comment = true
-            render(args[0], depth + '    ', options)
-        version: ->
-            options.version
-        include_and_minify: (args) ->
-            if (args.length > 1 and args[1].indexOf('c') isnt -1 and
-                     options.minify is false)
-                options.comment = true
-            d = render(args[0], depth + '    ', options)
-            if options.minify
-                return minify(array_flatten(d).join(''), options)
-            return d
-
-    console.warn(depth + " [.] Rendering", filename)
-
-    # no trailing whitespace
-    data = fs.readFileSync(filename, encoding='utf8').replace(/\s+$/, '')
-
-    content = []
-    if options.comment
-        content.push('\n// ' + depth + '[*] Including ' + filename + '\n')
-
-    elements = data.split(/<!--\s*([^>]+)\s*-->/g)
-    for i in [0...elements.length]
-        e = elements[i];
-        if i % 2 is 0
-            content.push(e)
-        else
-            p = e.split(' ')
-            content.push( tags[p[0]](p.slice(1)) )
-
-    if options.comment
-        content.push('\n// ' + depth + '[*] End of ' + filename + '\n')
-    return content
-
-
-main = ->
-    switches = [
-        ['-p', '--pretty', 'Prettify javascript']
-        ['-m', '--minify', 'Minify javascript']
-        ['-s', '--set-version [VERSION]', 'Set the value of version tag']
-    ]
-    options = {minify: false, toplevel: true, version: 'unknown'}
-    parser = new optparse.OptionParser(switches)
-    parser.on 'pretty', ->
-                   options.beautify = true
-    parser.on 'minify', ->
-                   options.minify = true
-    parser.on 'set-version', (_, version) ->
-                   options.version = version
-    filenames = parser.parse((process.ARGV || process.argv).slice(2))
-
-    content = for filename in filenames
-        render(filename, '', options)
-    content.push('\n')
-    process.stdout.write(
-        stringify_unicode(array_flatten(content).join('')),
-        'utf8')
-
-main()

package/src/runtimes/web/dom/sockjs/bin/run_testling.sh

@@ -1,135 +0,0 @@
-#!/bin/bash
-# Include a script with credentails:
-. .testling_env.sh
-# This script should set few Testling variables and should look more
-# or less like that:
-#
-# TESTLING_CRED=my@email.com:password
-# TUNNEL_PORT=12345
-# TUNNEL_USER=my_email_com
-#
-# First, you need to create browserling.com account. Set TESTLING_CRED
-# to email:password. Additionally, you must create a testling tunnel
-# using commands like that:
-#
-# curl -u $TESTLING_CRED "testling.com/tunnel" -sST ~/.ssh/id_rsa.pub
-# curl -u $TESTLING_CRED "testling.com/tunnel/open"
-#
-# After that set TUNNEL_PORT and TUNNEL_USER accordingly.
-#
-#
-
-browsers=(
-    # iexplore/6.0
-    # iexplore/7.0
-    # iexplore/8.0
-    # iexplore/9.0
-    # chrome/4.0
-    # chrome/5.0
-    # chrome/6.0
-    # chrome/7.0
-    # chrome/8.0
-    # chrome/9.0
-    # chrome/10.0
-    # chrome/11.0
-    # chrome/12.0
-    # chrome/13.0
-    # chrome/14.0
-    # chrome/15.0
-    chrome/canary
-    # firefox/3.0
-    # firefox/3.5
-    # firefox/3.6
-    # firefox/4.0
-    # firefox/5.0
-    # firefox/6.0
-    # firefox/7.0
-    # firefox/8.0
-    # firefox/nightly
-    # opera/10.0
-    # opera/10.5
-    # opera/11.0
-    # opera/11.5
-    # opera/next
-    # safari/5.0.5
-    # safari/5.1
-)
-
-BROWSERS=`echo ${browsers[@]}|tr ' ' ','`
-
-
-if [ "$TESTLING_CRED" = "" ] || \
-    [ "$TUNNEL_PORT" = "" ] || \
-    [ "$TUNNEL_USER" = "" ]; then
-    echo "Error: Please set following env variables: "\
-         "TESTLING_CRED TUNNEL_PORT TUNNEL_USER"
-    exit 1
-fi
-
-
-PIDFILE=.sshpidfile.pid
-
-if [ -e $PIDFILE ]; then
-    kill `cat $PIDFILE`
-    rm $PIDFILE
-fi
-
-
-
-cat > testling.js << EOF
-var test = require('testling');
-test('Testling Test Runner', function (t) {
-    t.createWindow('http://tunnel.browserling.com:$TUNNEL_PORT/unittests.html',
-        function(win, jq) {
-            jq(function() {
-                if(typeof win.QUnit === 'undefined') {
-                    t.log("No QUnit object in the window!");
-                    t.end();
-                } else {
-                    var q = win.QUnit;
-                    var module_name = '[unknown]';
-                    q.begin = function() {
-                        t.log(' [*] Start');
-                    };
-                    q.moduleStart = function(o) {
-                        module_name = o.name;
-                    };
-                    q.log = function(o) {
-                        var x = module_name + ': ' + o.message;
-                        t.ok(o.result, x);
-                        if(!o.result) {
-                            t.log(" [-] Failed: " + x);
-                        }
-                    };
-                    q.done = function(o) {
-                        t.log(' [*] Done ' + o.failed + ' ' + o.passed +
-                              ' ' + o.total + ' ' + o.runtime);
-                        t.end();
-                    };
-                }
-            });
-        });
-    // Dead man's switch
-    setTimeout(function(){
-        t.log("Emergency timeout ocurred");
-        t.end();
-    }, 5000);
-});
-EOF
-
-
-
-ssh -o "VerifyHostKeyDNS no" \
-    -NR $TUNNEL_PORT:localhost:8080 $TUNNEL_USER@tunnel.browserling.com &
-SSHPID=$!
-echo $SSHPID > $PIDFILE
-
-echo "[*] Running against: ${browsers[@]}"
-curl -u $TESTLING_CRED -sSNT testling.js \
-    "testling.com/?browsers=$BROWSERS&noinstrument=test.js"
-
-kill $SSHPID
-wait $SSHPID
-rm $PIDFILE
-
-curl -sSNu $TESTLING_CRED "testling.com/browsers"|tail -n 1

package/src/runtimes/web/dom/sockjs/package.json

@@ -1,18 +0,0 @@
-{
-	"name"        : "sockjs-client",
-	"author"      : "Marek Majkowski",
-    "version"     : "0.0.0-unreleasable",
-    "description" : "SockJS-client is a browser JavaScript library that provides a WebSocket-like object. SockJS gives you a coherent, cross-browser, Javascript API which creates a low latency, full duplex, cross-domain communication channel between the browser and the web server.",
-    "keywords"    : ["websockets", "websocket"],
-    "homepage"    : "http://sockjs.org",
-
-    "repository": {"type" : "git",
-                   "url" : "https://github.com/sockjs/sockjs-client.git"},
-    "devDependencies": {
-        "uglify-js"     : "1.2.5",
-        "coffee-script" : "1.2.x",
-        "optparse"      : "1.0.3",
-        "node-static"   : "0.5.9"
-    },
-    "main": "sockjs.js"
-}

package/src/runtimes/web/dom/sockjs/version

@@ -1 +0,0 @@
-0.3.4