Akka.Remote.Transport.Helios 1.3.3

The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org. Prefix Reserved
.NET Framework 4.5
Suggested Alternatives

Akka.Remote

Additional Details

No longer maintained. Use the default Akka.Remote transports instead.

There is a newer version of this package available.
See the version list below for details. 
dotnet add package Akka.Remote.Transport.Helios --version 1.3.3
NuGet\Install-Package Akka.Remote.Transport.Helios -Version 1.3.3
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="Akka.Remote.Transport.Helios" Version="1.3.3" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add Akka.Remote.Transport.Helios --version 1.3.3
#r "nuget: Akka.Remote.Transport.Helios, 1.3.3"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
// Install Akka.Remote.Transport.Helios as a Cake Addin
#addin nuget:?package=Akka.Remote.Transport.Helios&version=1.3.3

// Install Akka.Remote.Transport.Helios as a Cake Tool
#tool nuget:?package=Akka.Remote.Transport.Helios&version=1.3.3

(Legacy) Akka.NET remote transport layer based on Helios.

Product Compatible and additional computed target framework versions.
.NET Framework net45 is compatible.  net451 was computed.  net452 was computed.  net46 was computed.  net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.4.0-beta2 586 9/23/2019
1.4.0-beta1 536 7/19/2019
1.3.18 1,484 3/9/2020
1.3.17 2,130 12/20/2019
1.3.16 532 11/14/2019
1.3.15 1,467 9/23/2019
1.3.14 1,501 7/30/2019
1.3.13 926 4/30/2019
1.3.12 716 3/14/2019
1.3.11 864 12/18/2018
1.3.10 969 11/2/2018
1.3.9 952 8/23/2018
1.3.8 1,188 6/5/2018
1.3.7 1,156 5/15/2018
1.3.6 1,102 4/17/2018
1.3.5 1,053 2/22/2018
1.3.4 1,103 2/1/2018
1.3.3 1,045 1/19/2018
1.3.2 2,554 10/21/2017
1.3.1 1,138 9/5/2017
1.3.0 1,046 8/11/2017
1.2.3 1,197 7/10/2017
1.2.2 1,104 6/28/2017
1.2.1 1,095 6/23/2017
1.2.0 1,200 4/12/2017

Maintenance Release for Akka.NET 1.3**
The largest changes featured in Akka.NET v1.3.3 are the introduction of [Splint brain resolvers](http://getakka.net/articles/clustering/split-brain-resolver.html) and `WeaklyUp` members in Akka.Cluster.
Akka.Cluster Split Brain Resolvers**
Split brain resolvers are specialized [`IDowningProvider`](http://getakka.net/api/Akka.Cluster.IDowningProvider.html) implementations that give Akka.Cluster users the ability to automatically down `Unreachable` cluster nodes in accordance with well-defined partition resolution strategies, namely:
Static quorums;
Keep majority;
Keep oldest; and
Keep-referee.
You can learn more about why you may want to use these and which strategy is right for you by reading our [Splint brain resolver documentation](http://getakka.net/articles/clustering/split-brain-resolver.html).
Akka.Cluster `WeaklyUp` Members**
One common problem that occurs in Akka.Cluster is that once a current member of the cluster becomes `Unreachable`, the leader of the cluster isn't able to allow any new members of the cluster to join until that `Unreachable` member becomes `Reachable` again or is removed from the cluster via a [`Cluster.Down` command](http://getakka.net/api/Akka.Cluster.Cluster.html#Akka_Cluster_Cluster_Down_Akka_Actor_Address_).
Beginning in Akka.NET 1.3.3, you can allow nodes to still join and participate in the cluster even while other member nodes are unreachable by opting into the `WeaklyUp` status for members. You can do this by setting the following in your HOCON configuration beginning in Akka.NET v1.3.3:
```
akka.cluster.allow-weakly-up-members = on
```
This will allow nodes who have joined the cluster when at least one other member was unreachable to become functioning cluster members with a status of `WeaklyUp`. If the unreachable members of the cluster are downed or become reachable again, all `WeaklyUp` nodes will be upgraded to the usual `Up` status for available cluster members.
Akka.Cluster.Sharding and Akka.Cluster.DistributedData Integration**
A new experimental feature we've added in Akka.NET v1.3.3 is the ability to fully decouple [Akka.Cluster.Sharding](http://getakka.net/articles/clustering/cluster-sharding.html) from Akka.Persistence and instead run it on top of [Akka.Cluster.DistributedData, our library for creating eventually consistent replicated data structures on top of Akka.Cluster](http://getakka.net/articles/clustering/distributed-data.html).
Beginning in Akka.NET 1.3.3, you can set the following HOCON configuration option to have the `ShardingCoordinator` replicate its shard placement state using DData instead of persisting it to storage via Akka.Persistence:
```
akka.cluster.sharding.state-store-mode = ddata
```
This setting only affects how Akka.Cluster.Sharding's internal state is managed. If you're using Akka.Persistence with your own entity actors inside Akka.Cluster.Sharding, this change will have no impact on them.
Updates and bugfixes**:
[Added `Cluster.JoinAsync` and `Clutser.JoinSeedNodesAsync` methods](https://github.com/akkadotnet/akka.net/pull/3196)
[Updated Akka.Serialization.Hyperion to Hyperion v0.9.7](https://github.com/akkadotnet/akka.net/pull/3279) - see [Hyperion v0.9.7 release notes here](https://github.com/akkadotnet/Hyperion/releases/tag/v0.9.7).
[Fixed: A Source.SplitAfter Akka example extra output](https://github.com/akkadotnet/akka.net/issues/3222)
[Fixed: Udp.Received give incorrect ByteString when client send several packets at once](https://github.com/akkadotnet/akka.net/issues/3210)
[Fixed: TcpOutgoingConnection does not dispose properly - memory leak](https://github.com/akkadotnet/akka.net/issues/3211)
[Fixed: Akka.IO & WSAEWOULDBLOCK socket error](https://github.com/akkadotnet/akka.net/issues/3188)
[Fixed: Sharding-RegionProxyTerminated fix](https://github.com/akkadotnet/akka.net/pull/3192)
[Fixed: Excessive rebalance in LeastShardAllocationStrategy](https://github.com/akkadotnet/akka.net/pull/3191)
[Fixed: Persistence - fix double return of recovery permit](https://github.com/akkadotnet/akka.net/pull/3201)
[Change: Changed Akka.IO configured buffer-size to 512B](https://github.com/akkadotnet/akka.net/pull/3176)
[Change: Added human-friendly error for failed MNTK discovery](https://github.com/akkadotnet/akka.net/pull/3198)
You can [see the full changeset for Akka.NET 1.3.3 here](https://github.com/akkadotnet/akka.net/milestone/21).
| COMMITS | LOC+ | LOC- | AUTHOR |
| --- | --- | --- | --- |
| 17 | 2094 | 1389 | Marc Piechura |
| 13 | 5426 | 2827 | Bartosz Sypytkowski |
| 12 | 444 | 815 | Aaron Stannard |
| 11 | 346 | 217 | ravengerUA |
| 3 | 90 | 28 | zbynek001 |
| 3 | 78 | 84 | Maxim Cherednik |
| 2 | 445 | 1 | Vasily Kirichenko |
| 2 | 22 | 11 | Ismael Hamed |
| 2 | 11 | 9 | Nicola Sanitate |
| 1 | 9 | 10 | mrrd |
| 1 | 7 | 2 | Richard Dobson |
| 1 | 33 | 7 | Ivars Auzins |
| 1 | 30 | 11 | Will |
| 1 | 3 | 3 | HaniOB |
| 1 | 11 | 199 | Jon Galloway |
| 1 | 1 | 1 | Sam Neirinck |
| 1 | 1 | 1 | Irvin Dominin |