The Weird and The Wonderful

englebart wrote:

It seems that the sample code given should just put the result into a work queue so that the network IO can be overlapping the actual work without getting out of order...

Member 7931978 wrote:

This only works if you have only two calls to OnReceive() happening at once, no

Member 7931978 wrote:

what guarantee do you have that the "correct" thread will be the next one to acquire the lock?

private void StartAsyncReadLoop()
{
    ReadAsyncLoop(null);
}

private void ReadAsyncLoop(IAsyncResult state)
{
    try
    {
        if (state != null)
        {
            var length = _socket.EndReceive(state);
            // ...
        }

        // Ensure that only one level of recursion happens.
        if (state == null || !state.CompletedSynchronously)
            _socket.BeginReceive(..., ReadAsyncLoop, null);
        else
            // Maybe it's best to just always do this. Although considering how sockets use the thread pool
            // it's very likely overkill.
            ThreadPool.QueueUserWorkItem(_ => _socket.BeginReceive(..., ReadAsyncLoop, null));
    }
    catch (SocketException ex)
    {
        // ...
    }
}

@DaysBack 

SELECT CASE
    WHEN Field1 = 'Something #1' THEN 'Result #1'
    WHEN Field1 = 'Something #2' THEN 'N/A'
    WHEN Field1 = 'Something #3' THEN '(Empty)'
    ELSE 'N/A'
    END

djj55 wrote:

What was I thinking

if (someBooleanVariable == true)
    return true;
else
    return false;

return someBooleanVariable == true ? true : false;

return someBooleanVariable ? true : false

return someBooleanVariable

return someBooleanVariable ? Boolean.Parse(Boolean.TrueString) : Boolean.Parse(Boolean.FalseString);

return someBooleanVariable.ToString() == Boolean.TrueString? Boolean.Parse(Boolean.TrueString) : Boolean.Parse(Boolean.FalseString);