grpc-dotnet-namedpipes

grpc-dotnet-namedpipes copied to clipboard

error serializing large responses on client with remote pipe

3

see [issue 48](https://github.com/cyanfish/grpc-dotnet-namedpipes/issues/48) for context. Granted this case is probably not the norm: Remote piping (for now, going to be local soon for security reasons). The server code is 100%...

zachrybaker

allow fifo task execution

3

Expose task factory as a server context option so that FIFO task queue can be used. Address false error on disconnect.

zachrybaker

The following constructor is not public: ``` internal NamedPipeServer(string pipeName, NamedPipeServerOptions options, Action log) ``` Shouldn't it be public we so can register a custom `Action` for logging?

hmartinez82

Don't write trailers when PipeStream is disconnected.

2

HengWh

System.InvalidOperationException: The pipe is in a disconnected state!

2

There was a communication error during more than 20,000 Unary requests being executed. the server's error is as follows: caught by NamedPipeServer.Error event. System.InvalidOperationException: The pipe is in a disconnected...

NeverMorewd

Add serverside resilience for client disconnect during server streaming response

1

With 3.0, in a server streaming response, if the client leaves while the response stream is open, an uncaught RPC exception. throw new RpcException(new Status(StatusCode.Unavailable, "connection was unexpectedly terminated")); It...

zachrybaker

Added verification of PipeServer connection state

2

When testing in a multi-threaded environment with many connections per second, the following error was being generated: Cannot access a closed pipe. A brief adjustment was made to check the...

glaysons