Parimal Das wrote: > Please suggest. > 1. What i should include in this code to correct this hang?
It depends on what your code should do in this case. Do you want to wait a limited amount of time for the other side to reply? Or do you want to wait possibly forever? Your current code specifically elects to wait possibly forever, but then you complain when it waits possibly forever. If the user should interrupt it, then this is sensible. If not, then it's not. > 2. How to set read/write timeouts? Well, 'alarm' is the easiest way in toy code like this. You can reset the 'alarm' every time you receive a certain amount of data. It depends how you want to handle cases like where the other side 'dribbles' data at you. Decide how long is reasonable to wait, and code that. But this is another reason that blocking socket operations are difficult to use. In what realistic situation do you want to wait forever? So you make a blocking operation and then, surprise, have to work around the annoying fact that it blocks. DS ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
