home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 2001 May / SGI IRIX Base Documentation 2001 May.iso / usr / share / catman / p_man / cat3n / t_sync.z / t_sync
Encoding:
Text File  |  1998-10-20  |  6.1 KB  |  133 lines
  1.  
  2.  
  3.  
  4. tttt____ssssyyyynnnncccc((((3333NNNN))))                                                          tttt____ssssyyyynnnncccc((((3333NNNN))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      _tttt______ssss_yyyy_nnnn_cccc - synchronize transport library
  10.  
  11. SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  12.      _####_iiii_ffff_dddd_eeee_ffff ______XXXX_OOOO_PPPP_EEEE_NNNN______SSSS_OOOO_UUUU_RRRR_CCCC_EEEE
  13.      _####_iiii_nnnn_cccc_llll_uuuu_dddd_eeee _<<<<_xxxx_tttt_iiii_...._hhhh_>>>>
  14.      _####_eeee_llll_ssss_eeee
  15.      _####_iiii_nnnn_cccc_llll_uuuu_dddd_eeee _<<<<_tttt_iiii_uuuu_ssss_eeee_rrrr_...._hhhh_>>>>
  16.      _####_eeee_nnnn_dddd_iiii_ffff
  17.  
  18.      _iiii_nnnn_tttt _tttt______ssss_yyyy_nnnn_cccc _((((_iiii_nnnn_tttt _ffff_dddd_))))_;;;;
  19.  
  20. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  21.      For the transport endpoint specified by _ffff_dddd, _tttt______ssss_yyyy_nnnn_cccc synchronizes the data
  22.      structures managed by the transport library with information from the
  23.      underlying transport provider.  In doing so, it can convert a raw file
  24.      descriptor [obtained via _oooo_pppp_eeee_nnnn(2), _dddd_uuuu_pppp(2), or as a result of a _ffff_oooo_rrrr_kkkk(2) and
  25.      _eeee_xxxx_eeee_cccc(2)] to an initialized transport endpoint, assuming that file
  26.      descriptor referenced a transport provider.  This function also allows
  27.      two cooperating processes to synchronize their interaction with a
  28.      transport provider.
  29.  
  30.      For example, if a process _ffff_oooo_rrrr_kkkk_ssss a new process and issues an _eeee_xxxx_eeee_cccc, the new
  31.      process must issue a _tttt______ssss_yyyy_nnnn_cccc to build the private library data structure
  32.      associated with a transport endpoint and to synchronize the data
  33.      structure with the relevant provider information.
  34.  
  35.      It is important to remember that the transport provider treats all users
  36.      of a transport endpoint as a single user.  If multiple processes are
  37.      using the same endpoint, they should coordinate their activities so as
  38.      not to violate the state of the provider.  _tttt______ssss_yyyy_nnnn_cccc returns the current
  39.      state of the provider to the user, thereby enabling the user to verify
  40.      the state before taking further action.  This coordination is only valid
  41.      among cooperating processes; it is possible that a process or an incoming
  42.      event could change the provider's state _a_f_t_e_r a _tttt______ssss_yyyy_nnnn_cccc is issued.
  43.  
  44.      If the provider is undergoing a state transition when _tttt______ssss_yyyy_nnnn_cccc is called,
  45.      the function will fail.
  46.  
  47.      This function resides within both the X/Open compliant _llll_iiii_bbbb_xxxx_nnnn_eeee_tttt and the
  48.      SVR4 compliant _llll_iiii_bbbb_nnnn_ssss_llll Network Services libraries.  Network Services
  49.      applications which require X/Open compliance must link-load with _----_llll_xxxx_nnnn_eeee_tttt.
  50.      Network Services applications which require SVR4 compliance must link-
  51.      load with _----_llll_nnnn_ssss_llll.
  52.  
  53.      On failure, _tttt______eeee_rrrr_rrrr_nnnn_oooo may be set to one of the following:
  54.  
  55.      _TTTT_BBBB_AAAA_DDDD_FFFF              The specified file descriptor does not refer to a
  56.                         transport endpoint.
  57.  
  58.  
  59.  
  60.  
  61.  
  62.  
  63.                                                                         PPPPaaaaggggeeee 1111
  64.  
  65.  
  66.  
  67.  
  68.  
  69.  
  70. tttt____ssssyyyynnnncccc((((3333NNNN))))                                                          tttt____ssssyyyynnnncccc((((3333NNNN))))
  71.  
  72.  
  73.  
  74.      _TTTT_SSSS_TTTT_AAAA_TTTT_EEEE_CCCC_HHHH_NNNN_GGGG         The transport provider is undergoing a state change.
  75.  
  76.      _TTTT_SSSS_YYYY_SSSS_EEEE_RRRR_RRRR            A system error has occurred during execution of this
  77.                         function.
  78.  
  79. SSSSEEEEEEEE AAAALLLLSSSSOOOO
  80.      _dddd_uuuu_pppp(2), _eeee_xxxx_eeee_cccc(2), _ffff_oooo_rrrr_kkkk(2), _oooo_pppp_eeee_nnnn(2)
  81.  
  82. DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
  83.      _tttt______ssss_yyyy_nnnn_cccc returns the state of the transport provider on successful
  84.      completion and -1 on failure and _tttt______eeee_rrrr_rrrr_nnnn_oooo is set to indicate the error.
  85.      The state returned may be one of the following:
  86.  
  87.      _TTTT______UUUU_NNNN_BBBB_NNNN_DDDD            unbound
  88.  
  89.      _TTTT______IIII_DDDD_LLLL_EEEE             idle
  90.  
  91.      _TTTT______OOOO_UUUU_TTTT_CCCC_OOOO_NNNN           outgoing connection pending
  92.  
  93.      _TTTT______IIII_NNNN_CCCC_OOOO_NNNN            incoming connection pending
  94.  
  95.      _TTTT______DDDD_AAAA_TTTT_AAAA_XXXX_FFFF_EEEE_RRRR         data transfer
  96.  
  97.      _TTTT______OOOO_UUUU_TTTT_RRRR_EEEE_LLLL           outgoing orderly release (waiting for an orderly
  98.                         release indication)
  99.  
  100.      _TTTT______IIII_NNNN_RRRR_EEEE_LLLL            incoming orderly release (waiting for an orderly
  101.                         release request)
  102.  
  103.  
  104.  
  105.  
  106.  
  107.  
  108.  
  109.  
  110.  
  111.  
  112.  
  113.  
  114.  
  115.  
  116.  
  117.  
  118.  
  119.  
  120.  
  121.  
  122.  
  123.  
  124.  
  125.  
  126.  
  127.  
  128.  
  129.                                                                         PPPPaaaaggggeeee 2222
  130.  
  131.  
  132.  
  133.