SESSION |
Dijana Maričić, dijana_ri@hotmail.com |
The session protocol defines the format of
the data sent over the connections. The NFS uses
the Remote Procedure Call (RPC) for its session protocol. RPC may be built
on either TCP or
UDP. Login sessions uses TCP whereas NFS and broadcast use UDP. One of the services of the session layer is to manage dialogue control. Sessions can allow traffic to go in both directions at the same time, or in only one direction at a time. If traffic can only go one way at a time, the session layer can help keep track of whose turn it is. A related session service is token management. For some protocols, it is essential that both sides do not attempt the same operation at the same time. To manage these activities, the session layer provides tokens that can be exchanged. Only the side holding the token may perform the critical operation. Another session service is synchronization. Consider the problems that might occur when trying to do a two-hour file transfer between two machines on a network with a 1 hour mean time between crashes. After each transfer was aborted, the whole transfer would have to start over again, and would probably fail again with the next network crash. To eliminate this problem, the session layer provides a way to insert checkpoints into the data stream, so that after a crash, only the data after the last checkpoint has to be repeated. Izvori: http://www.webopedia.com/quick_ref/OSI_Layers.asp http://www2.rad.com/networks/1994/osi/session.htm
http://www.uwsg.iu.edu/usail/network/nfs/network_layers.html |