Dave Sexton
Dave Sexton
Consider updating the protocol to support raw C# input from clients. This will make it possible for JS clients to communicate over the new WebSocket provider. The idea is simple:...
Services that are themselves clients of upstream Qactive services (or any other `IQbservable` implementation) may wish to expose their `IQbservable` to downstream clients. Ensure that this is possible.
Ensure that sockets are terminated by the client rather than the server, wherever possible. Also ensure that observable termination yields deterministic results upon graceful shutdown; e.g., the client termination notification...
Write the size of messages (I/O) in bytes to the `Qactive` trace source.
Implement duplex support for `Task` similar to `IObservable`. Primary use case: When closing over a local method for duplex invocation, the server blocks until the client returns. This is inefficient;...
In building the original proof of concept I took some shortcuts with types for the sake of time. For clarity and performance, review all uses of types such as Tuple...
Implement all of the ToString methods and debugger view just like the real `Expression` implementations.
Check to see whether subject closures work as expected (I believe they do not at the moment). Shouldn't closing over a subject be treated as an IObservable closure by default?...
Rather than (or in addition to) protobuf (#3) or the `BinarySerializationFormatter` that is used by default, reuse my custom serialization (not open-sourced yet) via a new interface defined in a...