|
I'm currently working on something I call the BidirectionalTcpChannel for .NET Remoting which will be put in our Open Source Remoting Projects.
Rationale: The classic TCPChannel in Remoting allows the server to raise events (or employ callback interfaces) to notify its subscribed clients. The problem however is that the server will open a new tcp connection back to the client, which implies that events are simply not possible via NATs or firewalls. The BidirectionalTcpChannel will get rid of this limitation by switching from the classic request/response model of the TcpChannel to a message oriented model - thereby enabling reuse of the existing connection (the one which has been initiated by the client) to pass callbacks and events back to the client.
Status: I started working on this channel yesterday in the evening and currently have a basic message oriented tcp channel (still one-way!) using correlation IDs to map synchronous message calls onto the underlying async model.
I'll keep you updated ...
|