Remote Procedure Calls (RPC)
Vložit
- čas přidán 9. 09. 2024
- Operating System: Remote Procedure Calls (RPC)
Topics discussed:
This lecture explains about Remote Procedure Calls and how they are executed.
Follow Neso Academy on Instagram: @nesoacademy
Contribute: www.nesoacademy...
Memberships: bit.ly/2U7YSPI
Books: www.nesoacademy...
Website ► www.nesoacademy...
Forum ► forum.nesoacade...
Facebook ► goo.gl/Nt0PmB
Twitter ► / nesoacademy
Music:
Axol x Alex Skrindo - You [NCS Release]
#OperatingSystemByNeso #os #OperatingSystem #RemoteProcedureCalls
Here is what I learned from the video:
RPC stands for Remote Procedure Call.
- It is a communication protocol that allows a program running on one computer to execute code on a different computer over a network.
- It is often used in distributed systems where different components of the system are running on other computers
- For example, in a web application, the server might use RPC to communicate with a database server to retrieve data or to execute complex queries.
- RPC abstracts away many of the low-level details of network communication, making it easier for developers to build distributed systems.
- A client makes a remote procedure call to a server (RPC daemon), specifying the name (identifier) of a function to execute and any parameters that the function requires.
- The server receives the request, executes the specified function, and sends the result back to the client.
- The client can then continue executing its own code, using the result returned by the server.
• STUB:
- A stub is a piece of code that acts as a proxy (representative) for a remote procedure on the client side.
- The stub serves as an interface between the client program and the RPC system.
- It provides a way for the client program to make remote procedure calls to the server as if the procedure was a local function call.
- The stub is responsible for marshaling (assembling and arranging in order) the input parameters of the procedure, making the remote procedure call over the network to the RPC server, and then unmarshalling the results returned by the server.
• DAEMON*:
- An RPC daemon (or RPC server) is a program that runs in the background on a server and receives incoming requests for remote procedure calls from clients.
- The daemon is responsible for managing the communication between clients and the server, and for executing the requested procedures on the server.
* The MIT programmers thought demon would be an appropriate name for a background process that worked tirelessly to perform system chores. But instead of using the term demon, they used daemon, which is an older form of the word.
Thank you
These notes were much more useful than listening to the lecture, dude.
Excellent summary of this class :)
Great Summary
Thanks much for the summary. Far superior to the actual lecture, which was full of redundancy & irregular English.
RPC is a protocol that allows a program to request a service from a program in a different computer in a network. It is based on the message passing system as the processes are on separate computers. The message is composed of a function identifier and the corresponding parameters. This message is received by a RPC daemon listening on a specific port of the receiving computer. The result of the function call is passed back as a separate message to the requesting process.
Thanks non-fancy simple explaination!
Good job...was not expecting this to be this well-explained!
Your videos are the best.
RPC is for communication between processes that reside in different systems within a network. It abstract away the network details.
The client and server have an RPC daemon listening to each other port.
The client request to the server via a stub residing in the client side. It requests the server to do a service, in a form of a function. The server then sends back the result to the client.
The message is more complicated than packets of data.
The message contain the function identifier and the parameter of that function.
The parameters are marshaled to be transmitted over the network.
Messages are sent from the client stub to server stub by message passing.
RPC stands for remote procedure call. It abstracts away network details, so that make it easier for developers to work with. It is used for distributed systems. For example, a server want to request to the database server to get or modify data.
Stub acts as an interface between the client and the RPC system, so that the client can communicate with the server as is locally.
Stub is responsibile for parameter marshaling (assemble and arrange parameters) for client and unmarshaling for the server.
RPC daemon or RPC server is a program running in the background on the server. It receives incomming requests for RPC from the client and execute the request.
Perfect explanation
Bro this complicated stuff is explained so well. My professor couldn't explained for shit
lol
so real
well explained appreciated
Thanks a lot . This is an amazing explanation♥♥
Many thanks. This video is really helpful
Incredibly helpful, Thanks so Much!🙏
Thank you so much
was looking for a comprehnsive explanation and this was it!
incredible video, much thanks
Simple and so clear great explanation.
Thank you 🙏🏼
thanks for the clear explanation :)
Thanks alot for the video.
Thank you so much
awesomeeeeeeeeeeeeeeeeeee explanation.....thank you very much neso academy
As im from biology background ....so i felt very difficult to understand programing nd how the computer works i side.....bt u made my path easy sir ......tq u sm ....feeling so happy 😊😊make more videos sir ....
It would be more interesting to watch if you use more animation and less text. We've got books. All theory is there but we want explanation with simple animation so that we don't have to read all those big paragraphs
Yes😪
Hi
You are right
yooo, this guy basically spent a bunch of time to put this together for free and you complaining? Go and create your own visual if you are not able to understand concepts like this just by text. 😂😂😂
Totally agree
Man!! your explanation is awesome. Keep it up
Thanks teacher :D
very well explained very compliments !!!!!!!!!!I tried so many times to find something that explains me so well but i didn't find it .
Thanks so much
Impressive explanation, thanks a lot and greetings from argentina!
Great video, great explanation !!!
Very helpful. Thank you.
So, RPC are remote procedural calls. RCS is used for processes to communicate when they're residing in different systems. Procedures are involved. Stubs are allocated to processed at each end.
Thank you so much for great lecture.
Great working sir
Please upload videos on posix multithreading
Thank you for the info...
Thankyou sir
Thank you
I love how he keeps repeating the statements, these lectures are not one of types of video you just take a peek on, you actually learn from it and shove it deep into your brain
Thank you, sir. I've been searching a lot for something like this.
A good video for Intro to RPC, the intuition is strong, however, just a little repetitive (which helps to retain, though)
You explain so well. Thank you so much
Excellent explanation! Thank you very much!
thnx
Great lecture though a pic showing rpc would have been more helpful
Make videos on compiler design ,machine learning artificial inteñligence ,cloud computing ....nd abt more techies tutorial ....so that it will be very helpful for students like me ....i hope u teachers make best vídeos....
Sir, please make video on Computer Architecture.
شكرا جزيلا
Here is a summary of the video:
Remote Procedure Calls (RPC) is a protocol that allows a program to request a service from a program located on another computer on a network without having to understand the network's details. In simpler terms, RPC enables communication between processes residing in different systems connected over a network.
Here are the key differences between RPC and IPC:
Communication scheme: RPC uses message-based communication, whereas IPC can use either shared memory or message passing.
Messages: RPC messages are well-structured and contain an identifier of the function to execute and the parameters to pass to that function, while IPC messages are just packets of data.
Stubs: RPC uses stubs on both the client and server sides to hide the details of communication from the processes. IPC does not use stubs.
Here's how RPC works:
Client invokes a remote procedure: The client process calls a local stub, passing it the parameters for the remote procedure.
Stub marshals parameters: The stub marshals the parameters into a form that can be transmitted over the network.
Stub transmits message to server: The stub transmits a message to the server using message passing.
Server stub receives message: A similar stub on the server side receives the message and unmarshals the parameters.
Server stub invokes procedure: The server stub invokes the remote procedure on the server, passing it the unmarshaled parameters.
Procedure executes: The remote procedure executes on the server.
Server stub marshals return values: If necessary, the server stub marshals the return values into a form that can be transmitted over the network.
Server stub transmits message to client: The server stub transmits a message to the client using message passing.
Client stub receives message: The client stub receives the message and unmarshals the return values.
Client stub returns results: The client stub returns the results to the client process.
Thank you..😇
But we use Message passing system for communicating between 2 procesess on different devices connected to network?
Yeah brother, RPC is itself a kind of message passing system. But the difference between the regular Message-passing and RPC is that, As RPC has to perform on two different systems, it needs to be processed in a way that the message passing can happen over the network. If both the processes resided in the same system, we can just send a message from the sender process to the kernel and then the receiver process gets that message through the kernel. But in RPC, the function related to the process resides in a different system, so certain parameter passing and processing of the parameters is necessary.
could you bring out the difference between HTTP ans RPC ?
Thanks
Nice
Hello sir
I haive doubt
What will be the output
printf("%d","");
Output is 173 but how
This question was asked in my bca exam
Plz help me sir
Yes NYC
Sir please upload the issues/limitations of RPC asap.
Your description should start with a link or put one of those clickable links in the video to the referenced video in the beginning. A tip for a tip :-). Another tip is to not pin your own comment to the top of the comments section. That section is for comments of your viewers.
Wow you have a lot of videos! Thank you for all of them! I would give you $5/month if I had that kind of time and money to just give away and watch all your videos. But still, Thank YOU for putting them up. I don't understand what "Join" is or how it works. But if it was a one-time donation, tip, gift, or something like that I would definitely give you more than just $5.
Every youtuber pins his or her cmnt giving info about this video or other more detail about it. I don't think u have any idea how to run a youtube channel..useless
If you don't have this much time..how did you get this much time to write review and advices...llllooollllzzzz...double standard people
popular question !!!
What is time to do null RPC?
Sir why your not uploading network theory
Give him a chance to make the video. Don't demand free content. Ask for it.
need file systems
Is the operating System course that easy? I am not a computer science student. Please someone answer.
:)
You have just copied the book as it is.
too wordy
Omg
thank you