Skip to content
Cycle.js driver for deepstream.io
TypeScript
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
dist
examples
src
.gitignore
.travis.yml
CHANGELOG.txt
LICENSE.txt
README.md
package.json

README.md

cycle-deepstream

Build Status npm version Coverage Status Join the chat at https://gitter.im/EnigmaCurry/cycle-deepstream

A Cycle.js driver for the deepstream.io javascript client.

Allows realtime communication between multiple clients and your cluster of deepstream servers. A self-hosted firebase replacement.

simple example advanced example

(above: the simple example running in three browser windows, and the advanced example simulating two mobile devices.)

Run Demo

Get the code:

git clone https://github.com/EnigmaCurry/cycle-deepstream.git
cd cycle-deepstream
npm install

Run the simple example:

npm run simple

Or run the advanced demo:

npm run advanced

Usage Notes

No formal docs exist for this yet. This driver implements most of the deepstream API methods. In Cycle.js you never use imperative calls directly (code with side-effects), so cycle-deepstream wraps these calls into a driver with an API that uses plain-javascript objects to define actions (actions.ts).

For instance, calling record.subscribe returns an object that just describes what action to perform:

> const {actions} = require('cycle-deepstream')
> actions.record.subscribe('some-record')
{ action: 'record.subscribe',
  name: 'some-record',
  events: {},
  scope: undefined }

This action describes the appropriate deepstream API method to call and some additional arguments. In this case they are:

  • action - the deepstream API method name
  • name - the name of the deepstream record to subscribe to
  • events - the names of the record events that we wish to subscribe to. The default is to subscribe to all of them, eg: {'record.existing': true, 'record.change': true, 'record.discard': true, 'record.delete': true, 'record.error': true }.
  • scope - this is a common argument to all of the methods, it specifies a particular ID to the request that is also applied to the response. This allows your code to know whether a particular event is due to your actions by filtering the event stream on this same ID. If no scope is defined, a default scope is used that is shared amongst all other requests that also don't use a scope. This mostly affects record.discard, as this will only discard the subscription of the record with the same scope defined.

This plain object is sent to the driver in it's input stream and processed by the driver asynchronously. When a deepstream event comes from the server, the driver passes this information to the output stream and back into your cycle application. Events of this sort look like this:

{ event: 'record.change',
  name: 'some-record',
  data: {
    foo: 'bar'
  },
  scope: undefined }

This event is the first response to our subscribe action above, consisting of the data of the existing content of the 'some-record' object in deepstream's database. Subseqent events would be more 'record.change' events or possibly 'record.delete' etc.

There's a helper function to apply scopes to actions:

> const {actions} = require('cycle-deepstream')
> const scope = actions.scope()    /* This returns a function, a 'scope applier' */
> scope(actions.record.get('some-record'))
{ action: 'record.get',
  name: 'some-record',
  scope: 'j1jlj39z5ue7chjjdi4g' }    /* A randomly generated scope ID */
> scope.scope   /* The scope ID is available on the object, even though it's a function */
'j1jlj39z5ue7chjjdi4g'

The events you receive for the record will now have the scope j1jlj39z5ue7chjjdi4g applied to them so that you can filter on it in your own code.

There are two examples that show general usage. The end-to-end test show comprehensive usage.

Features

Deepstream API Implementation:

  • Client

    • login
    • logout
    • events:
      • onConnectionChange
      • client.error
      • login.success
      • login.failure
      • logout
  • Records:

    • record.subscribe
      • once subscribed, will emit events:
        • record.change
        • record.discard
        • record.delete
        • record.error
    • record.set
    • record.get
    • record.snapshot
    • record.discard
    • record.delete
    • record.listen
    • record.unsubscribe
      • Not implemented. Use record.discard instead.
  • Lists:

    • list.subscribe
      • once subscribed, will emit events:
        • list.change
        • list.entry-existing
          • This emits individual events, like list.entry-added, but for each existing entry in the list.
          • Note, this is a driver level event, not a part of the Deepstream API.
        • list.discard
        • list.delete
        • list.error
        • list.entry-added
        • list.entry-moved
        • list.entry-removed
    • list.getEntries
    • list.setEntries
    • list.addEntry
    • list.removeEntry
    • list.discard
    • list.delete
    • list.unsubscribe
      • Not implemented. Use list.discard instead.
  • Events:

    • event.subscribe
    • event.unsubscribe
    • event.emit
    • event.listen
    • event.unlisten
  • Presence:

    • presence.subscribe
    • presence.unsubscribe
    • presence.getAll
  • RPC:

    • rpc.make
    • rpc.provide - I think this makes no sense to implement in cycle?
You can’t perform that action at this time.