Remote Procedure Call
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
seminar class
Active In SP

Posts: 5,361
Joined: Feb 2011
16-02-2011, 04:58 PM

.ppt   RPC.ppt (Size: 333.5 KB / Downloads: 73)
Remote Procedure Call
RPC Timeline
RCP Components

• Protocol Stack
– BLAST: fragments and reassembles large messages
– CHAN: synchronizes request and reply messages
– SELECT: dispatches request to the correct process
• Stubs Bulk Transfer (BLAST)
• Unlike AAL and IP, tries to recover from lost fragments
• Strategy
– selective retransmission
– aka partial acknowledgements
BLAST Details
• Sender:
– after sending all fragments, set timer DONE
– if receive SRR, send missing fragments and reset DONE
– if timer DONE expires, free fragments
• Receiver:
– when first fragments arrives, set timer LAST_FRAG
– when all fragments present, reassemble and pass up
– four exceptional conditions:
• if last fragment arrives but message not complete
• send SRR and set timer RETRY
• if timer LAST_FRAG expires
• send SRR and set timer RETRY
• if timer RETRY expires for first or second time
• send SRR and set timer RETRY
• if timer RETRY expires a third time
• give up and free partial message
BLAST Header Format
• MID must protect against wrap around
• NumFrags indicates number of fragments
• FragMask distinguishes among fragments
– if Type=DATA, identifies this fragment
– if Type=SRR, identifies missing fragments
Request/Reply (CHAN)
• Guarantees message delivery
• Synchronizes client with server
• Supports at-most-once semantics
CHAN Details
• Lost message (request, reply, or ACK)
– set RETRANSMIT timer
– use message id (MID) field to distinguish
• Slow (long running) server
– client periodically sends “are you alive” probe, or
– server periodically sends “I’m alive” notice
• Want to support multiple outstanding calls
– use channel id (CID) field to distinguish
• Machines crash and reboot
– use boot id (BID) field to distinguish
Synchronous vs Asynchronous Protocols
• Asynchronous interface
send(Protocol llp, Msg *message)
deliver(Protocol llp, Msg *message)
• Synchronous interface
call(Protocol llp, Msg *request, Msg *reply)
upcall(Protocol hlp, Msg *request, Msg *reply)
• CHAN is a hybrid protocol
– synchronous from above: call
– asynchronous from below: deliver

Important Note..!

If you are not satisfied with above reply ,..Please


So that we will collect data for you and will made reply to the request....OR try below "QUICK REPLY" box to add a reply to this page

Quick Reply
Type your reply to this message here.

Image Verification
Please enter the text contained within the image into the text box below it. This process is used to prevent automated spam bots.
Image Verification
(case insensitive)

Possibly Related Threads...
Thread Author Replies Views Last Post
  the call paper concept priya puppy 0 360 28-01-2014, 08:41 PM
Last Post: priya puppy
  Controlling Remote Desktop pdf seminar projects maker 0 242 26-09-2013, 01:03 PM
Last Post: seminar projects maker
  Remote-Controlled Home Automation Systems with Different Network Technologies Report study tips 0 318 12-06-2013, 04:52 PM
Last Post: study tips
  ppt on Remote Display solutions for mobile cloud computing study tips 0 456 07-06-2013, 03:28 PM
Last Post: study tips
  Procedure Oriented Vs Object Oriented PPT study tips 0 290 02-03-2013, 12:50 PM
Last Post: study tips
  Remote Login: Telnet PPT study tips 0 438 15-02-2013, 10:05 AM
Last Post: study tips
  To study Remote procedure call i.e RPC protocol study tips 0 466 14-02-2013, 12:52 PM
Last Post: study tips
  Remote WAP Report project girl 0 473 01-02-2013, 04:06 PM
Last Post: project girl
  Introduction to Remote Sensing & GIS PPT project girl 0 540 01-02-2013, 12:00 PM
Last Post: project girl
  Cyborg Beetles: The Remote Radio Control of Insect Flight pdf project girl 0 402 28-01-2013, 03:17 PM
Last Post: project girl