David Glasser d049bf7506 Use faye-websocket for server-to-server DDP ...

This matches what the SockJS server uses; now we only need to understand
and fix bugs in the implementation of one websocket npm module.

Some notes:

  - I actually trust that it's possible to close a connection before it
    successfully connects, which allows me to simplify the code a
    lot (since there shouldn't be multiple connections active per
    ClientStream). I put in some assertions to make sure this is the
    case, though.  (Note that this module also has a simpler model,
    where there's a single object representing the client connection,
    not a "client" object that spawns "connections".)

  - We now print connect errors as well as post-connect errors.  (This
    required adding a flag to keep tests quiet since it makes an
    expected-to-fail-to-connect connection.)  We need a better approach
    to stream error handling, though.

  - We used to have a test to make sure that a certain not-user-visible
    callback is called within a Fiber; structuring the code such that
    this test is still possible would lead to the code being less
    consistent and harder to read, so I dropped the test.

  - Fix a few bugs where we weren't using Meteor.setTimeout.

2014-02-27 15:20:43 -08:00

..

.gitignore

Extract retry package from livedata

2013-12-23 12:53:58 -08:00

package.js

Add missing 'random' dependency to retry

2014-01-06 15:14:39 -08:00

retry.js

Use faye-websocket for server-to-server DDP

2014-02-27 15:20:43 -08:00