grpc-dotnet | open source , high-performance remote procedure call

by grpc C# Version: v2.54.0-pre1 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(4)Vulnerabilities Install Support

kandi X-RAY | grpc-dotnet Summary

grpc-dotnet is a C# library typically used in Web Services applications. grpc-dotnet has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

gRPC is a modern, open source, high-performance remote procedure call (RPC) framework that can run anywhere. gRPC enables client and server applications to communicate transparently, and simplifies the building of connected systems.

Support

Quality

Security

License

Reuse

Support

grpc-dotnet has a medium active ecosystem.

It has 3669 star(s) with 706 fork(s). There are 119 watchers for this library.

It had no major release in the last 12 months.

There are 78 open issues and 1104 have been closed. On average issues are closed in 73 days. There are 5 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of grpc-dotnet is v2.54.0-pre1

Quality

grpc-dotnet has 0 bugs and 0 code smells.

Security

grpc-dotnet has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

grpc-dotnet code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

grpc-dotnet is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

grpc-dotnet releases are available to install and integrate.

Installation instructions are not available. Examples and code snippets are available.

grpc-dotnet saves you 6273 person hours of effort in developing the same functionality from scratch.

It has 13284 lines of code, 0 functions and 722 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of grpc-dotnet

Get all kandi verified functions for this library.

grpc-dotnet Key Features

No Key Features are available at this moment for grpc-dotnet.

grpc-dotnet Examples and Code Snippets

No Code Snippets are available at this moment for grpc-dotnet.

Community Discussions

Trending Discussions on grpc-dotnet

C# & nginx - upstream timed out

GRPC .Net Core server & C++ client: Https connection fails, "No common application protocol between client/server"

gRPC failed to connect to all addresses or DNS resolution failed for service

grpc-dotnet server streaming of local process output

QUESTION

C# & nginx - upstream timed out

Asked 2021-Aug-12 at 10:50

I have a Problem with my grpc connections and nginx.

So, i've got these things : a client, a server, nginx. They all run on the same machine.

The client does some network scanning and is supposed to send it's results to the server,

The server is supposed to take the scanning-results and put them into a database. The server is based on ASP.Net - See appsettings.json The client and server use "grpc-dotnet" with "protobuf". Both also use the SSL certificate and generally they both work as expected.

The nginx proxy is supposed to be used as a Reverse-Proxy -> Clients only need to know one Endpoint for all their Requests. Nginx is only configured to pass grpc requests, nothing else.

First of all, almost all grpc requests do work. But they stop working, if the request gets too big. I dont know the exact size, but it must be under 180kb.

(180kb is the size of the scan results.In a test, sending half of these results succeded, where sending all did not. Custom test data (with the same class of course) did show the same results. If they got too big, it stopped working)

Without nginx, there are no errors while sending data from client to server. With nginx however, the client does recieve a HTTP 504 error.

Content of error.log (nginx)

2021/07/27 13:27:28 [error] 21464#7952: *66 upstream timed out (10060: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat) while sending request to upstream, client: 127.0.0.1, server: , request: "POST /UI.Remoting.Discovery.Contract.DiscoveryService/SaveDiscoveryResult HTTP/2.0", upstream: "grpcs://127.0.0.1:30053", host: "localhost:30051"

"Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat" translates to :

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

nginx.conf - i did try many configurations - they do not solve my problems. The configurations shown below are just to show you, which ones i've tested, but there might be missing some. I've tested them in multiple different arrangements and selectively tested out each configuration in different areas (server, http, location)

...

ANSWER

Answered 2021-Aug-12 at 10:50

It seems like there actually is a bug in the current nginx versions. I've posted a new ticket in nginx's ticket system. https://trac.nginx.org/nginx/ticket/2229

Source https://stackoverflow.com/questions/68547210

QUESTION

GRPC .Net Core server & C++ client: Https connection fails, "No common application protocol between client/server"

Asked 2021-Mar-12 at 00:25

I'm trying to get a GRPC server (written in .NET core) and client (written in C++) to communicate over a SSL/TLS-secured channel.

The server targets "netcoreapp3.1", and depends on "Grpc.AspNetCore" version 2.28.0. The server code itself is basically copied from the official grpc repo's examples. The Startup.cs and Program.cs are not too interesting on their own & probably aren't the problems, so I just uploaded them to a gist (do note the call to UseHttps though). Everything builds, and a toy .NET core GRPC client (sources for that here) connects over HTTPS just fine

Unfortunately, I need to be using a C++ client to make the connection. Theoretically, the process is simple: get the .pfx file corresponding to the certificate passed to the UseHttps call, use it to create a server.crt via openssl, and use that to create a secure channel for the C++ client like so:

...

ANSWER

Answered 2021-Mar-12 at 00:25

I later submitted another question with more details, and with an "answer." You can check that out here

Source https://stackoverflow.com/questions/66464983

QUESTION

gRPC failed to connect to all addresses or DNS resolution failed for service

Asked 2021-Feb-12 at 08:37

I am currently trying to get an example for gRPC working. I am using a C# Asp.NET Core WebApi as the server and I try to connect to it via a Python client.

Ressources

My proto file:

...

ANSWER

Answered 2021-Feb-11 at 18:12

Please see https://github.com/grpc/grpc/blob/master/doc/naming.md

the use of "https" is not correct

Source https://stackoverflow.com/questions/66107965

QUESTION

grpc-dotnet server streaming of local process output

Asked 2020-Jun-08 at 16:34

I am working with grpc-dotnet in 3.1 for a project. On the server side, the grpc call will be executing a local system process (such as binaries or scripts). The issue I am having is the streaming of the redirected output from the process back over the grpc client. All I am getting right now is the first line of output. Here is my testing code.

...

ANSWER

Answered 2020-Jun-08 at 16:34

This might be because you're writing to the ResponseStream from an event handler, which is not necessarily being called on the right async context for the stream.

Take a look at CliWrap which wraps the whole process execution thing in a very nice API, including a ListenAsync method which returns an IAsyncEnumerable that you can await foreach over and write the output to the stream.

Borrowing from the README, it would look something like this:

Source https://stackoverflow.com/questions/62251866

Community Discussions, Code Snippets contain sources that include Stack Exchange Network