close Warning: Can't synchronize with repository "(default)" ("(default)" is not readable or not a Git repository.). Look in the Trac log for more information.

Changes between Version 2 and Version 3 of Proto/cModules/c0HostProtocolStack/c0Configuration


Ignore:
Timestamp:
Sep 8, 2015, 8:04:20 PM (9 years ago)
Author:
kais
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Proto/cModules/c0HostProtocolStack/c0Configuration

    v2 v3  
    6767CSYN_TO=800000
    6868
    69 # whether to use a transport protocol with end-to-end reliability semantics.
     69# whether to use a transport protocol with end-to-end
     70# reliability semantics.
    7071TRANS_RELIABLE=true
    7172
    72 # The variable settings below are considered only if TRANS_RELIABLE is set to true
    73 # Transport layer message with a chunk count equal to or greater than this threshold will be sent with NACK-based end-to-end error recovery.
     73# The variable settings below are considered only if
     74# TRANS_RELIABLE is set to true
     75# Transport layer message with a chunk count equal to
     76# or greater than this threshold will be sent with
     77# NACK-based end-to-end error recovery.
    7478TRANS_CHK_COUNT_NACK_THRESH=3
    7579
    76 # NACK Timeout value at sender. If the sender is sending a message of N chunks, after N * TRANS_SEND_NACK_TIMEOUT milliseconds, the chunks will be destroyed, and memory is garbage collected.
     80# NACK Timeout value at sender. If the sender is
     81# sending a message of N chunks, after
     82# N * TRANS_SEND_NACK_TIMEOUT milliseconds, the chunks
     83# will be destroyed, and memory is garbage collected.
    7784TRANS_SEND_NACK_TIMEOUT=2000
    7885
    79 # NACK Timeout value at the receiver. If the error recovery mechanism is NACK and the message is not complete before N * TRANS_RECV_NACK_TIMEOUT, for a message of N chunks, the receiver will transmit a NACK message to the sender. Setting this value more conservatively to favor network-based recovery for handling disconnection.
     86# NACK Timeout value at the receiver. If the error
     87# recovery mechanism is NACK and the message is not
     88# complete before N * TRANS_RECV_NACK_TIMEOUT, for a
     89# message of N chunks, the receiver will transmit a
     90# NACK message to the sender. Setting this value more
     91#conservatively to favor network-based recovery for
     92# handling disconnection.
    8093TRANS_RECV_NACK_TIMEOUT=20000
    8194}}}