Aaron Stannard

@Horusiath question: think it'd be easier to prove this as a concept inside of Akka.IO initially? Fewer moving parts than Akka.Remote. I'm open to the idea. One of the problems...

@IgorFedchenko is investigating replacing our current `SocketAsyncEventArgs` implementation with System.IO.Pipelines inside Akka.IO. The plan is to dramatically increase the throughput of Akka.IO first and then use it as the transport...

Based on the work @IgorFedchenko did, looks like this is out of scope for v1.4.0. Need to add .NET Standard 2.1 targeting to get any real benefit out of this.

@ismaelhamed looking at doing this for Artery in 1.5, so this should be done soon-ish

I've made a YT video for this but we need to incorporate it into the docs.

For the Hyperion implementation of this, probably best to add the filtering inside Hyperion itself rather than inside the `HyperionSerializer` in Akka.NET - that way it becomes a feature of...

Also, our network security documentation needs a facelift - don't think we've touched that since Akka.NET v1.2.0.

First step for Hyperion is complete - actually implementing this feature inside the Serializer: https://github.com/akkadotnet/Hyperion/pull/242 Still need to do a new Hyperion release, expose this through Akka.Serialization.Hyperion, and then document...

Stage 2 is underway: https://github.com/akkadotnet/akka.net/pull/5208 - this will be released in Akka.NET v1.4.24

cc @eaba