Remote CSP Channel. Send messages between separate JavaScript processes like they're in the same place.

github.com/getify/remote-csp-channel

Problem

The full read on this project is a sign-in away — what it solves, who it serves, and where it sits in the market.

Audience

The full read on this project is a sign-in away — what it solves, who it serves, and where it sits in the market.

Market

The full read on this project is a sign-in away — what it solves, who it serves, and where it sits in the market.

Pricing

The full read on this project is a sign-in away — what it solves, who it serves, and where it sits in the market.

Vaya's read on this project

Problem, audience, market, and the verdict — sign in to see it.

Updates

November 2015

tweaking README Nov 21
adding README docs Nov 19
tweaking example Nov 19
tweaking example Nov 19
tweaking example code for consistency Nov 19
adding 'examples' directory Nov 19
fixing package.json dependencies list Nov 19
renaming 'TransportChildProc' to 'TransportNodeStream' Nov 19
renaming 'childproc' to 'nodestream' Nov 19
tweaking lib internal param names, adding 'childproc' transport Nov 13
adding 'socketio' transport Nov 12
adding default package.json for webworker transport Nov 11
fixing bug where deferring setting up transport caused lost messages … Nov 11
adding protection against overriding a transport definition Nov 10
tweaking context value in webworker transport Nov 10
fixing sequencing bug when remote-action comes before local action Nov 10
externalizing CSP channel factory method specification Nov 10
tweaking API for RemoteCSPChannel.defineTransport(..) Nov 10
renaming 'bridge' code terminology to 'transport' Nov 10
renaming 'bridges' dir to 'transports' Nov 10