Releases: kuzzleio/kuzzle
Releases · kuzzleio/kuzzle
0.8.0
- Implemented protocol plugins support
- Added a new plugin configuration argument: "loadedBy", taking "all", "server" or "worker". Its purpose is to limit plugin installation & loading only by the corresponding kuzzle instance type
- Added socket.io plugin as a default plugin
- removed socket.io dependency
- updated unit and functional tests
- updated plugin documentation
- REST protocol is now linked to the port 7511 instead of 7512
- Reworked plugin installation so that servers and workers can act independantly. This removes the "normal" errors we got when starting Kuzzle
- Added a banner to inform users when a Kuzzle instance is up, running, and accepting requests
Others:
- removed winston dependency
0.7.2
To remove unnecessary Kuzzle dependencies from the router controller and to prepare the incoming protocol plugins, this pull request changes the way the router controller handles worker responses, following @stafyniaksacha suggestion:
- renamed
core/responseListener
tocore/workerListener
to make it easier to understand what it does - removed all references to the
workerListener
from the router controller. Also removed empty promises handling. Promises resulting from calls to the funnel controller now always resolve to the according responseObject - the main Kuzzle object now contains a global
workerListener
instance - controllers behind the funnel controller now always return a promise resolving to the awaited response, either directly, or by returning the result of
workerListener.add
- the
workerListener
now awaits worker responses using the internal broker, and resolve/reject the stored promises, letting the router controller respond to the requesting client. It doesn't notify directly anymore.
0.7.1
- implemented the possibility to get realtime collections using the existing "listCollections" API method
- updated unit tests, functional tests and API documentation
- tidied up the
readController
unit tests - removed remnants of the old
roomName
argument in thehotelClerk.removeCustomerFromAllRooms
unit tests - added missing unit tests on the
removeRooms
method of theadminController
0.7.0
- Support multi-index (persistent & realtime layers)
- Add : CRUDL operations on indexes
- Add : _createIndex role policy
- Add : _createCollection role policy
- Add : internal cache for index hierarchy (used by when checking policies)
- Refactor : ReadEngine & WriteEngine allways fulify promises with a ResponseObject : no need to recreate it in worker when Response is delayed
- Refactor : Change api route to /api/v1
- Refactor : Mock elasticsearch in units tests
0.6.5
Added a lazy-loading repositories() getter
Useful for authentication plugins, and probably other kinds of plugins in a future.
0.6.3
0.6.1
0.6.0
- Fix: the responseListener core component waited for queries not forwarded to workers, effectively creating a memleak
- Publishing messages is now done using the
publish
route from thewrite
controller, instead of using apersist
flag in thecreate
route create
,createOrUpdate
anddelete
requests now notify subscribed users as-if the requests itself was a realtime message- additional arguments can be provided in the
subscribe.on
request, allowing to filter notifications depending on their state, scope, or if this is a user event - kuzzle rooms are now multi-channel, each channel corresponding to a subscription configuration. A user can subscribe multiple times on the same room using different channels
- subscribers now have to listen to the
channel
tag provided in the subscribe.on response, instead of theroomId
. Thechannel
tag is only that: the channel on which the user needs to listen in order to receive notifications