New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Design / API Changes upcoming #239

Open
rogeralsing opened this Issue Jun 10, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@rogeralsing
Collaborator

rogeralsing commented Jun 10, 2018

We have been doing some major API re-work on the .NET side of things.
AsynkronIT/protoactor-dotnet#404

This will cause some breaking changes once implemented for Go.
But it is for the greater good, consistent API, better testability and observability.

@linkerlin

This comment has been minimized.

Show comment
Hide comment
@linkerlin

linkerlin Jul 17, 2018

What's going on?
It has a plan?

linkerlin commented Jul 17, 2018

What's going on?
It has a plan?

@cpx86

This comment has been minimized.

Show comment
Hide comment
@cpx86

cpx86 Jul 17, 2018

Contributor

@linkerlin The mentioned issue specifies the changes we're doing. Mainly it is 1) removing PID.Tell/Request in favor of the newly introduced RootContext (to allow for better middleware support) and 2) renaming of some core concepts, e.g. Tell-> Send, LocalProcess->ActorProcess, LocalContext->ActorContext

From a user's POV it shouldn't be too bloody, we're mainly restructuring the API surface a bit. It is breaking though, hence the heads-up 😅

Contributor

cpx86 commented Jul 17, 2018

@linkerlin The mentioned issue specifies the changes we're doing. Mainly it is 1) removing PID.Tell/Request in favor of the newly introduced RootContext (to allow for better middleware support) and 2) renaming of some core concepts, e.g. Tell-> Send, LocalProcess->ActorProcess, LocalContext->ActorContext

From a user's POV it shouldn't be too bloody, we're mainly restructuring the API surface a bit. It is breaking though, hence the heads-up 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment