Outgoing middleware design broken

[rogeralsing]

Currently the outgoing middleware has all the parts it needs internally.
but, the Process.SendUserMessage has the signature: (PID pid, object message, PID sender)
which does not allow us for sending outgoing headers.
And if we try to send a MessageEnvelope, things get double wrapped if there is a sender as the LocalProcess checks for sender and wraps the current message in another MessageEnvelope.

TLDR;

We should change the signature of SendUserMessage to just (PID pid, object message) and do the envelope wrapping already in Request

[cpx86]

Do we have the same issue in Go? I.e. is this a porting issue or was the solution broken from the start?

[rogeralsing]

Yes, same issue there
We really should have a Proto.Actor meta/design issue tracker

[cpx86]

Yeah maybe we should have a new "protoactor" repo for cross-cutting concerns. That could also be used for core documentation that's not specific to any language.

[cpx86]

Or we can just repurpose the "gam-web" repo - rename it to "protoactor" and use it for both the website and for general/meta issue tracking.

[rogeralsing]

relates to #127

[rogeralsing]

This has been fixed