使用 TaskCompletionSource 作为 WaitHandle 替代品是否可以接受?

2024-02-27

我的代码处理与远程主机的 TCP 连接,ConcurrentQueue存储传出消息。它旨在在单线程中运行。连接的生命周期包含在RunAsync而一个单独的对象包含连接的“公共状态”:

class PublicState
{
    internal readonly ConcurrentQueue<Message> OutgoingMessageQueue = new ConcurrentQueue<Message>();
    internal TaskCompletionSource<Object> OutgoingMessageTcs = null;

    internal readonly TaskCompletionSource<Object> ConnectedTcs = new TaskCompletionSource<Object>();

    public void EnqueueMessages(IEnumerable<Message> messages)
    {
        foreach( Message m in messages ) this.OutgoingMessageQueue.Enqueue( m);
        if( this.OutgoingMessageTcs == null ) this.OutgoingMessageTcs = new TaskCompletionSource<Object>();
        this.OutgoingMessageTcs.SetResult( null );
    }
}

static async Task RunAsync(IPEndPoint endPoint, PublicState state)
{
    using( TcpClient tcp = new TcpClient() )
    {
        await tcp.ConnectAsync( endPoint.Address, endPoint.Port ).ConfigureAwait(false);

        Byte[] reusableBuffer = new Byte[ 4096 ];

        using( NetworkStream ns = tcp.GetStream() )
        {
            state.ConnectedTcs.SetResult( null );

            Task<Int32> nsReadTask = null;

            while( tcp.Connected )
            {
                if( !state.writeQueue.IsEmpty )
                {
                    await WriteMessagesAsync( ... ).ConfigureAwait( false );
                }

                if( ns.DataAvailable )
                {
                    await ReadMessagesAsync( ... ).ConfigureAwait( false );
                }

                // Wait for new data to arrive from remote host or for new messages to send:
                if( state.OutgoingMessageTcs == null ) state.OutgoingMessageTcs = new TaskCompletionSource<Object>();
                if( nsReadTask == null ) nsReadTask = ns.ReadAsync( reusableBuffer, 0, 0 ).ConfigureAwait( false );

                Task c = await Task.WhenAny( state.OutgoingMessageTcs,  nsReadTask ).ConfigureAwait( false );
                if( c == state.OutgoingMessageTcs.Task ) state.OutgoingMessageTcs = null;
                else if( c == nsReadTask ) nsReadTask = null;
            }
        }
    }
}

像这样使用:

public async Task Main(String[] args)
{
    PublicState state = new PublicState();
    Task clientTask = Client.RunAsync( new IPEndPoint(args[0]), state );

    await state.ConnectedTcs.Task; // awaits until TCP connection is established

    state.EnqueueMessage( new Message("foo") );
    state.EnqueueMessage( new Message("bar") );
    state.EnqueueMessage( new Message("baz") );

    await clientTask; // awaits until the TCP connection is closed
}

这段代码可以工作,但我不喜欢它:感觉就像我正在使用TaskCompletionSource这意味着代表一个实际的任务或某种后台操作,而我实际上正在使用TaskCompletionSource作为一种廉价的EventWaitHandle。我没有使用EventWaitHandle因为它是IDisposable(我不想冒泄漏本地资源的风险)并且它缺乏WaitAsync or WaitOneAsync方法。我可以用SemaphoreSlim(这是可等待的,但包含一个EventWaitHandle)但我的代码并不能真正代表信号量的良好使用。

我使用的是TaskCompletionSource<T>可以接受,或者是否有更好的方法来“取消等待”执行RunAsync当一个项目被添加到OutgoingMessageQueue?

我觉得这是“错误”的另一个原因是TaskCompletionSource<T>只能使用一次,之后需要更换。我热衷于避免无关的分配。


如果我理解正确的话 - TPLBufferBlock可能就是你所需要的。模拟电流Enqueue is Post,您可以通过以下方式接收下一个值ReceiveAsync扩展方法。

So with BufferBlock你的代码变成这样:

class PublicState {
    internal readonly BufferBlock<Message> OutgoingMessageQueue = new BufferBlock<Message>();
    internal readonly TaskCompletionSource<Object> ConnectedTcs = new TaskCompletionSource<Object>();

    public void EnqueueMessage(Message message) {
        this.OutgoingMessageQueue.Post(message);
    }
}

static async Task RunAsync(IPEndPoint endPoint, PublicState state) {
    using (TcpClient tcp = new TcpClient()) {
        await tcp.ConnectAsync(endPoint.Address, endPoint.Port).ConfigureAwait(false);

        Byte[] reusableBuffer = new Byte[4096];

        using (NetworkStream ns = tcp.GetStream()) {
            state.ConnectedTcs.SetResult(null);

            Task<Int32> nsReadTask = null;
            Task<Message> newMessageTask = null;
            while (tcp.Connected) {
                // Wait for new data to arrive from remote host or for new messages to send:
                if (nsReadTask == null)
                    nsReadTask = ns.ReadAsync(reusableBuffer, 0, 0);
                if (newMessageTask == null)
                    newMessageTask = state.OutgoingMessageQueue.ReceiveAsync();
                var completed = await Task.WhenAny(nsReadTask, newMessageTask).ConfigureAwait(false);
                if (completed == newMessageTask) {
                    var result = await newMessageTask;
                    // do stuff
                    newMessageTask = null;
                }
                else {
                    var bytesRead = await nsReadTask;
                    nsReadTask = null;
                }
            }
        }
    }
}

作为奖励,这个版本(我认为)是线程安全的,而你当前的版本不是,因为你正在做非线程安全的事情OutgoingMessageTcs来自潜在的多个线程(线程RunAsync和线程EnqueueMessages呼叫者)。

如果由于某种原因你不喜欢BufferBlock- 您可以使用AsyncCollection from Nito.AsyncExnuget 包的方式完全相同。初始化变为:

internal readonly AsyncCollection<Message> OutgoingMessageQueue = new AsyncCollection<Message>(new ConcurrentQueue<Message>());

并获取:

if (newMessageTask == null)
   newMessageTask = state.OutgoingMessageQueue.TakeAsync();
本文内容由网友自发贡献,版权归原作者所有,本站不承担相应法律责任。如您发现有涉嫌抄袭侵权的内容,请联系:hwhale#tublm.com(使用前将#替换为@)

使用 TaskCompletionSource 作为 WaitHandle 替代品是否可以接受? 的相关文章

随机推荐