deepstream.io

Release description

Fixing header copying issue from uws http and websocket requests

[3.1.0] - 2017.09.25

Features

• a new standardised logging API with debug, info, warn and error methods
• the presence feature can now be used on a per user basis. The online status of individual users can be queried for as well as subscribed to. Check out the tutorial on our website here

Improvements

• perMessageDeflate option can now be passed to uws, courtesy of @daviderenger #786
• various fixes and performance improvements to the subscription registry #780, courtesy of @ronag.

Fixes

• allow updating and writing to Lists via the HTTP API #788 courtesy of @rbarroetavena
• no data when sending HTTP requests is now considered undefined, rather than null #798.

Miscellaneous

• internal refactor to pull e2e client operations into framework and abstract from Cucumber steps.

[3.0.1] - 2017.08.14

Features

• Added a restart option to deepstream service CLI
• deepstream will now write to a pid file at /var/run/deepstream/deepstream.pid while running as a service
• Authentication and permission plugins can now be configured via config and will be resolved as normal plugins. Either a path or name will need to be provided at the top level, and any options specified will also be passed in.

Miscellaneous

• Updated various dependencies as well as our dependency on uws.

[3.0.0] - 2017.07.26

Features

HTTP API

Enabling clients to create, read, update and delete records, emit events, request RPCS
and read presence using a JSON bulk request/response format via HTTP.

• The HTTP API is enabled by default on PORT 8080 and can be configured in the
  connectionEndpoints -> http section of deepstream's config.yml
• To disable the HTTP API set the above config to null

PHP Client Support

The above HTTP API makes deepstream.io compatible with the deepstream PHP client

Multi Endpoint Architecture

The deepstream 3.0 release lays the groundwork for multiple combinable endpoints/protocols,
e.g. GraphQL or Binary to be used together. It also introduces a new endpoint type enabling
developers to write their own. Please note - at the moment it is not possible to run multiple subscription
based endpoints (e.g. websocket) simultaneously.

Message Connector Discontinuation

To address the scalability issues associated with the message connector interface's coarse topics
deepstream will move to a build-in, high performance p2p/small world network based clustering approach, available
as an enterprise plugin. The current message connector support is discontinued.

Miscellaneous

• Moved end-to-end tests into this repository from deepstream.io-client-js.
• Replaced javascript-state-machine dependency with custom state machine.

Fixes

• Improved handling of invalid record names.

[2.4.0] - 2017.07.01

Features

• Added new CLI command, including:

  • deepstream daemon
    This command forks deepstream and monitors it for crashes, allowing it to restart automatically to avoid downtime

  • deepstream service add
    This command allows you to create an init.d or systemd script automatically and add it to your system.

  sudo deepstream service --help
  Usage: service [options] [add|remove|start|stop|status]
  Add, remove, start or stop deepstream as a service to your operating system
  

• Added brew cask support

You can now install easily install deepstream on your mac using brew cask install deepstream driven by config files within /user/local/etc/deepstream/conf

Fixes

• Fix issue where certain invalid paths would return 'Invalid Type' on the server.
• Fix issue in request/response where selecting a remote server as not done uniformly.

[2.3.7] - 2017.06.20

Fixes

• Fix issue where using both .0. and [0] within a json path resulted in inserting into an array. However, when using other SDKs such as Java they would be treated as an Object key or array index.
• Fix issue where nested array access/manipulation didn't work via json paths.

Compatability Issue

Due to the nature of this fix, it may result in compatability issues with applications that used json paths incorrectly ( using .0. intead of [0] ). Please ensure you change those before upgrading.

[2.3.6] - 2017.06.12

Fixes

• Fix for issue #703
  where record deletions were not being propagated correctly within a cluster.
• Fixes config-loading issue present in the binary release of 2.3.5.

[2.3.5] - 2017.06.12

Fixes

• Hardcode v3.0.0-rc1 dependency on javascript-state-machine, as v3.0.1 causes deepstream.io startup to fail

[2.3.4] - 2017.06.02

Fixes

• Hot path needs to store values in the correct format

Fixes

• Binary config files have the correct latest structure
• Fix an issue where heavy concurrent writes on the same record fail

Fixes

• Fixing a connection data regression where it wasn't formatted the same as pre 2.3.0

Features

• Adds "storageHotPathPatterns" config option.
• Adds support for setData(): upsert-style record updates without requiring that a client is
  subscribed to the record. This uses a new 'CU' (Create and Update) message. The setData() API
  is up to 10x faster than subscribing, setting, then discarding a record.
• Support for connection endpoint plugins.

Enhancements

• Significant performance improvements stemming from message batching.

Miscellaneous

• Moved uws into a connection endpoint plugin.
• Explicit state-machine that initializes and closes dependencies in a well-defined order.

[2.2.2] - 2017.05.03

Enhancements

• Adds support for custom authentication and permissioning plugins.
• Adds support for generic plugins.

Fixes

• Added check to ensure subscriptions are not removed from distributed state registry prematurely.

[2.2.1] - 2017.04.24

Enhancements

• Unsolicited RPCs now get a INVALID_RPC_CORRELATION_ID message

Fixes

• RPC lifecycles have been improved and don't throw exceptions on response after a timeout by ronag
• Correct options now being passed into the RuleCache, courtesy of ralphtheninja