Folks, my experiments with the TcpClient and TcpListener classes last week worked well, my server could "push" logging information out to the client(s) with relatively easy code. However, it's all untyped, it's one-way and I feel that sending binary blobs is really old fashioned and crude.
So in the modern .NET world, what are my choices for strongly-typed duplex communication? If I was doing this on a LAN I'd use Remoting which uses a contract and has async callbacks, but Remoting doesn't normally work between remote networks. What other choices are there? *Greg K*
