These are chat archives for akkadotnet/akka.net
ActorPathserialization problems with simple ignore attributes. Don't you think that using a introducing a specialized
ISurrogateinterface to work around default Akka serializer is a little hacky?
Yes, the default Java serialization works for cyclic references. When you serialize object C, the field will contain a backreference to the already-serialized object A instead of serializing it again.
PingPongbenchmark reflect any internal serialization overhead?
SerializeAllMessages = onsetting right?
ISurrogatefor specific messages and allow to preserve reference handling for JSON.NET? For the second case it would be nice to check perf benchmark changes
PipeToinside actors and how it works. Included some animated gifs I made to illustrate the concurrent parts. Any feedback on this before I promote / publish this tomorrow? http://petabridge.com/blog/akkadotnet-async-actors-using-pipeto/