readable [3]

Enables or disables the idle-conversation readability check.




Default: yes


The readability check queries the communications stack regarding the local endpoint for the conversation to determine if a receive operation will return immediately. This can be true if there is data to be read, or if the peer has closed its end of the conversation, or for certain failures. If the conversation is readable, MFCS will attempt to receive a single byte. Any received data is buffered for later processing; if MFCS gets an indication that the conversation is closed or failed, it is processed accordingly. Typically, there is no requirement to disable this check; this option is provided in case a problem is found with the readability check mechanism.