Releases: launchdarkly/dotnet-eventsource
Releases · launchdarkly/dotnet-eventsource
3.1.5
[3.1.5] - 2018-08-29
Duplicate of 3.1.4, created due to a problem in the release process.
3.1.4
[3.1.4] - 2018-08-29
Fixed
- Fixed a bug that prevented the event source from reconnecting to the stream if it received an HTTP error status from the server (as opposed to simply losing the connection).
3.1.3
[3.1.3] - 2018-08-13
Fixed
- The reconnection attempt counter is no longer shared among all EventSource instances. Previously, if you connected to more than one stream, all but the first would behave as if they were reconnecting and would have a backoff delay.
3.1.2
[3.1.2] - 2018-08-02
Changed
- The SDK was referencing some system assemblies via
<PackageReference>, which could cause dependency conflicts. These have been changed to framework<Reference>s. A redundant reference toSystem.Runtimewas removed.
Fixed
- If the stream connection fails, there should be an increasing backoff interval before each reconnect attempt. Previously, it would log a message about waiting some number of milliseconds, but then not actually wait.
3.1.1
[3.1.1] - 2018-06-28
Removed
- Removed an unused dependency on Newtonsoft.Json.
3.1.0
[3.1.0] - 2018-06-01
Added
- The new class
ConfigurationBuilderprovides a validated fluent builder pattern forConfigurationinstances. - The HTTP method and request body can now be specified in
ConfigurationBuilderor in theConfigurationconstructor. The default is still to useGETand not send a request body.
3.0.0
Changed
- Switched logging framework to Common.Logging.
2.2.1
2.2.0
[2.2.0] - 2018-01-19
Added
- Exposed
EventSourceServiceCancelledExceptionas a public class.
Changed
- Removed unused and transitive dependencies.
- Added a reference to the Apache 2.0 license in
LaunchDarkly.EventSource.csproj - Improved logging. Thanks @JeffAshton!