All Versions
99
Latest Version
Avg Release Cycle
17 days
Latest Release
-

Changelog History
Page 6

  • v4.2.2 Changes

    September 17, 2019

    🛠 Fix

    ➕ Adding health-checks for all ws based endpoints.

  • v4.2.1 Changes

    September 17, 2019

    🛠 Fix

    ✂ Remove conflicting port for those starting using node with an empty config object.

    👌 Improvement

    🌲 Limit the dead socket log to reduce insane spam.

  • v4.2.0 Changes

    September 09, 2019

    Feat

    Two new connection endpoints have been added. They are currently experimental and will be properly 📚 announced with associated documentation.

    👍 One endpoint is mqtt! This allows us to support mqtt auth (using username and password), retain using records and QoS 1 using write acks. The only issue is since mqtt only supports one sort ⚡️ of concept (with flags distinguishing them) we bridge both events and records together. That means if you subscribe to 'temperature/london', you'll get the update from both a client doing event.emit('temperature/london') and record.setData('temperature/london').

    The second endpoint is ws-json which allows users to interact with deepstream by just passing through json serialized text blobs instead of protobuf. This is mainly to help a few people trying to write SDKs without the hassle of a protobuf layer.

    Value also injects a name variable which allows you to reference the name your currently in. Useful for cross referencing.

    🛠 Fix

    👀 Subscription registry seemed to have a massive leak when it came to dead sockets! This has now been fixed. The sockets seemed to have gotten the remove event deleted earlier in their lifecycle which prohibited it from doing a proper clean up later.

  • v4.1.0 Changes

    August 30, 2019

    [4.1.0] - 2019.08.30

    Feat

    Backwards compatibility with V3 clients / text protocol using a ws-text connection endpoint

    👍 This has a couple of small differences, like has is no longer supported and snapshot errors
    are exposed using the global error callback instead of via the response. Otherwise all the e2e
    ✅ tests work, and best of all you can run both at the same time if you want to run JS 4.0
    and Java 3.0 simultaneously!

    It is worth keeping in mind there is a small CPU overhead between switching from V3 custom deepstream
    encoding to JSON (V4), so it is advised to monitor your CPU when possible!

    - type: ws-text
    options:
        # port for the websocket server
        port: 6021
        # host for the websocket server
        host: 0.0.0.0

  • v4.0.6 Changes

    August 19, 2019

    [4.0.6] - 2019.08.19

    Feat

    👍 Allow SUBSCRIBE and READ without CREATE actions, for clients that are in read only mode

    👌 Improvement

    ➕ Adding declaration types (thank you @Vortex375!)

  • v4.0.5 Changes

    August 09, 2019

    👌 Improvement

    ➕ Adding meta objects to logs and monitoring for easier tagging to monitoring solutions

  • v4.0.4 Changes

    August 05, 2019

    [4.0.4] - 2019.08.05

    🛠 Fix

    • Don't buffer error messages in relation to connections, otherwise the client will get the close event first
    • Ignore ping messages during the connecting and authenticating stages

  • v4.0.3 Changes

    August 04, 2019

    [4.0.3] - 2019.08.04

    🛠 Fix

    • 🔌 Notify monitoring plugin of all messages sent out individually

  • v4.0.2 Changes

    August 03, 2019

    [4.0.2] - 2019.08.03

    🔋 Features

    • 🐳 Alpine docker image

    🛠 Fix

    • Override the http port and host correctly

  • v4.0.1 Changes

    July 31, 2019

    [4.0.1] - 2019.07.31

    👌 Improvements

    • Exit immediately if HTTP server port is occupied
    • 🔌 When using debug, log exact error to why a plugin could not be loaded