v3.0.0
[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'sconfig.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-machinedependency with custom state machine.
Fixes
- Improved handling of invalid record names.