Skip to content
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

Improved Erlang process representation in Python #28

Open
2 tasks
kvakvs opened this issue Sep 3, 2018 · 1 comment
Open
2 tasks

Improved Erlang process representation in Python #28

kvakvs opened this issue Sep 3, 2018 · 1 comment

Comments

@kvakvs
Copy link
Contributor

kvakvs commented Sep 3, 2018

Better feature mirroring from Erlang in Python:

  • Better defined API for Python handlers of Pyrlang events in Process class
  • Exception handling/crash imitation with links/monitors triggering and process ending
@kvakvs kvakvs added this to To Do in Make Pyrlang Great Sep 3, 2018
@s2hc-johan
Copy link
Collaborator

@kvakvs poking around the Process and gen_server a bit. Thinking of restructuring a bit in gen.py So one is apparently something for the RPC thing and the other one is for gen_server I'm guessing.

What about if we make generic message names, so messages is whats get passed around all the time right, so we could create:

  • GenIncomingCall
  • GenIncomingCallRPC (or maybe just GenIncomingRPC if cast isn't an option)
  • GenIncomingInfo
  • GenIncomingCast

if not that we could use parse_incoming_msg that returns something like:

  • (call, object)
  • (cast, object)
  • (info, object)
  • ... if I missed somethig

Either way we can make a nice matching to know where to go after that in the gen_server. We also create a quite nice interface helping if someone needs to override.

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

No branches or pull requests

2 participants