jasterv/grpc-slides
1
0
Fork 0
mirror of https://codeberg.org/JasterV/grpc-slides.git synced 2026-04-26 18:40:03 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update notes

Browse source
This commit is contained in:
JasterV 2025-06-13 11:20:43 +02:00
parent a147b19583
commit 5f23b7258b
1 changed files with 20 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

33
docs/learning_grpc.md
View file

@ -21,15 +21,6 @@ note:
The concept dates back to 1976 [1]
---
![image](assets/rpc_architecture.png)
<a style="font-size: 20px;" href="http://birrell.org/andrew/papers/ImplementingRPC.pdf">
http://birrell.org/andrew/papers/ImplementingRPC.pdf
</a>
note:
Building applications that required communicating with a separate machine was difficult and required big expertise
This RPC implementation aimed to make it highly efficient (network-wise) as well as as simple to use as non-remote procedures.
@ -40,13 +31,29 @@ They aimed to provide secure communications with RPC.
Things were shared in plain non secured text.
Back in the time they already used a tool to auto-generate the client and server stubs:
`But the user-stub and server-stub are automatically generated, by a program called Lupine.`
[1] WHITE, J. E. A high-level framework for network-based resource sharing. In Proc. National Computer Conference, (June 1976).
---
![image](assets/rpc_architecture.png)
<a style="font-size: 20px;" href="http://birrell.org/andrew/papers/ImplementingRPC.pdf">
http://birrell.org/andrew/papers/ImplementingRPC.pdf
</a>
note:
The program structure would be based in the concept of Stubs.
Five pieces of program are involved when making an RPC call:
User -> User-stub -> RPC communications package (known as RPCRuntime) -> server-stub -> the server.
They auto-generated the client and server stubs:
`The user-stub and server-stub are automatically generated, by a program called Lupine.`
---
### Interface Definition Language