Skip to content

Latest commit

 

History

History
31 lines (24 loc) · 3.54 KB

release_notes.md

File metadata and controls

31 lines (24 loc) · 3.54 KB
Raw

Release Notes

NuGet packages for the last good build on master are available via AppVeyor (see Artifacts). The simplest way to work with this is to create a local NuGet source in Visual Studio for a shared directory visible to your team and download the packages there.

When we push a collection of functionality it is available via nuget.org and symbol files are published to symbolsource.org

This section lists features in master, available by AppVeyor, but not yet deployed to nuget.org.

Master

  1. Fixed an issue where you could not have multiple UsePolicy or FallbackPolicy attributes on a single handler.

Release 3.0.129

  1. We now support a Fallback method on IHandleRequests which is intended to be used for compensating or emergency action when a Handle method cannot be executed. The [FallbackPolicy] attribute supports the pipeline calling the Fallback method for you, in the event of either any exception bubbling into the handler, or a broken circuit exception bubbling into the handler.
  2. Fix issue with RabbitMQ consumers running on a High Availability cluster not cancelling properly after cluster failover.
  3. Fixed bug with config section duplication BrighterCommand#52
  4. Added functionality so after a specified number of unacceptable message (unable to read from queue or map message) a connection is shutdown, by default unacceptable message are acked and dropped. BrighterCommand#51

Release 3

  1. Refactored IAmAMessagingGateway into a IAmAMessageConsumer and IAmAMessageProducer to support differing approaches to producing and consuming messages for a particular flavour of Message-Oriented-Middleware. These changes are a breaking binary change for users of earlier versions.
    1. NOTE: IF YOU USE TASK QUEUES PLEASE SAVE YOUR SERVICEACTIVATORCONNECTIONS IN YOUR APP.CONFIG AS THE V2.0.1 BRIGHTER.SERVICEACTIVATOR UNINSTALL WILL DELETE THEM (FIXED FOR V3)
  2. Created an IAmAChannel abstraction to allow differing Application Layer dependencies for the Work Queue
  3. Upgraded Packages we depend on, including RabbitMQ. There is still an issue with our having a hard dependency on a RabbitMQ client that might vary from your RabbitMQ client version, but as a NuGet package there are few workarounds. We suggest building from source where this issue is problematic, for now.
  4. Significant stability improvements on the RabbitMQ client
    1. Fixed issues around re-connection of the client leading to lost messages.
    2. Fixed issues when explicitly closing and re-opening connections
    3. Provided support for a RequeueException to requeue messages that are 'out-of-time' to help with resequencing.
    4. We now dispose of channels aggressively on closure, instead of waiting for garbage collection
  5. Moved from Common.Logging to LibLog These changes are a breaking binary change for users of earlier versions.
  6. We now call Release for all RequestHandler<> derived handlers that we construct from an IAmAHandlerFactory, not just those that implement IDisposable.
  7. Note that the RestMS server is NOT ready for production usage. It's primary value, as of today, is an alternative to RabbitMQ for design purposes. It is hoped to produce a stable version for use as a ControlBus in a future release.