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

why named rpc ? #54

Closed
binnn6 opened this issue Oct 2, 2017 · 3 comments
Closed

why named rpc ? #54

binnn6 opened this issue Oct 2, 2017 · 3 comments

Comments

@binnn6
Copy link

binnn6 commented Oct 2, 2017

As for now, rpc is just used callback across. It's confused me. What about rename it to callback?
And port is confusing too. Maybe ipc should be used ? Just wondering.

@igorsysoev
Copy link
Contributor

RPC is remote procedure call. This is exactly what it does in unit.
Ports are similar to Mach ports.

@binnn6
Copy link
Author

binnn6 commented Oct 2, 2017

This so-called rpc is just for callback, and a msg type(_NXT_PORT_MSG_RPC_READY, _NXT_PORT_MSG_RPC_ERROR). Rpc is too big a name for this. Or maybe rpc_callback could be used.

@VBart
Copy link
Contributor

VBart commented Oct 2, 2017

RPC is a form of IPC and "remote" doesn't necessarily mean physically remote, but in a different virtual address space.

@binnn6 binnn6 closed this as completed Oct 3, 2017
4141done pushed a commit to 4141done/unit that referenced this issue Sep 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants