All Versions
59
Latest Version
Avg Release Cycle
49 days
Latest Release
931 days ago
Changelog History
Page 3
Changelog History
Page 3
-
v2.1.0 Changes
- ๐ Features
- Inject an error reporter in various zmq outbound socket operations
- Allow local message dispatch when the bus is stopping
- ๐ Bug fixes
- Ensure all replayed messages are acked to the persistence
- Support unserializable messages in dispatch error handling
- Code cleanup
- Migrate to VS2017 project file
- ๐ Features
-
v2.0.0 Changes
โก๏ธ This version introduces a major breaking change: a dedicated
TransportMessage
is now used to forward messages to the persistence service, instead of sending aPersistMessageCommand
. An updated persistence service is still able to process commands sent by old peers, but an old persistence service is not be able to process the new TransportMessage. Thus the persistence service must be updated first.- ๐ Features
- Support batch message processing with
IBatchMessageHandler
- Execute the initial segment of async handlers on the dispatch queue
- Use a synchronization context to queue up async continuations
- Support batch message processing with
- ๐ Performances
- Improve
TransportMessage
serialization performance (200x for reads, 3x for writes) - Make
MessageTypeId
a value type with cached members - Reduce serializations (#62)
- Improve
- Code cleanup
- Make OriginatorInfo.SenderMachineName internal
- Use cake for build scripts
- ๐ Features
-
v1.5.1 Changes
- ๐ Features
- Make error publication optional with
IBusConfiguration.IsErrorPublicationEnabled
- Make error publication optional with
- Code cleanup
- Use
Task.Run
to invoke command completion tasks instead of customTaskScheduler
- Use
- ๐ Features
-
v1.5.0 Changes
- ๐ Bug fixes
- Use a circuit-breaker to reduce unresolvable peer performance impact
- Code cleanup
- Make internal a few testing types that were not intented to be available outside Zebus
- ๐ Bug fixes
-
v1.3.1 Changes
- ๐ Bug fixes
- Error codes of locally handled commands are returned properly
- Empty subscription updates are not sent to the Directory
- ๐ Bug fixes
-
v1.3.0 Changes
A client using this version needs its Directory server to be at least in 1.1 for dynamic subscriptions to work properly
- ๐ Features
- Subscription updates are made by message type instead of as a big atomic change to improve subscriptions performance
- ๐ Features
-
v1.2.13 Changes
Republished the NuGet because the version number was not incremented in 1.2.12
-
v1.2.12 Changes
- ๐ Bug fixes
- Pulled the new
MessageDispatcher
filter feature up toIMessageDispatcher
- Pulled the new
- ๐ Bug fixes
-
v1.2.11 Changes
- ๐ Bug fixes
- Fixed NuGet dependencies
- ๐ Bug fixes
-
v1.2.10 Changes
- ๐ Features
- The inbound port is no longer sticky, since the feature was not relevant anymore (we are no longer relying on ZMQ's buffers)
- The
MessageDispatcher
can be provided with a message type filter
- ๐ Features