POC wrote: > Are you saying there needs to be more to the above logic in order to > use NSPR calls after a select call?
Yes. Sometimes a PR_Recv() on a PRFileDesc results in a write() on the underlying socket. Sometimes when that write() returns EWOULDBLOCK, the only way the connection will make further progress would be for the application to wait until the underlying socket becomes writeable and then call PR_Recv() (or, as it happens, PR_Send()).
