This project has moved and is read-only. For the latest updates, please go here.

TCP Qbservable Provider suggestions

Topics: Experimental, Reactive (Rx)
Aug 15, 2012 at 7:13 PM

First off, this library is absolutely brilliant!

I was wondering how difficult would it be to abstract away TCP and instead expose access to serializing the data to a stream and managing that stream.

In my application, I've been looking to develop something very similar to what is already implemented except the serialization would be in JSON rather than binary and the communication mechanism would be using SignalR rather than TCP sockets.

Allowing the user to control the stream would give them the ability to add an encryption layer as well as package the stream with additional data for routing and authentication.


Aug 17, 2012 at 12:37 AM

Hi Shaun,

WCF as the transport abstraction is part of the road map; however, I'm not sure yet when I'll get around to it.

I'm also interested in how it could work with SignalR.  I'll create a work item for it.

Thanks for the feedback.

- Dave

Aug 17, 2012 at 12:38 AM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.