Flurl.Http
Simple.OData.Client
Our great sponsors
| Flurl.Http | Simple.OData.Client | |
|---|---|---|
| 21 | - | |
| 4,009 | 327 | |
| - | 0.9% | |
| 8.2 | 8.5 | |
| 18 days ago | 13 days ago | |
| C# | C# | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Flurl.Http
-
Building a Gateway to Netflix API: A Developer's Guide
Flurl and others
- Serilog with Enrich.WithExceptionDetails() causing Maximum destructuring depth reached on FlurlHttpException
-
Integration Testing Confusion?
Is Flurl.HTTP the same as https://flurl.dev/ I assume? (It doesn't mention a specific http package)
-
Converting javascript fetch code to equivalent C# code
As far as your code goes, take a look at flurl (https://flurl.dev/). It is oh so much cleaner and more readable than the httpclient stuff.
- how do i make api call?
-
ASP.NET Core - how to properly make a GET request?
I would also add flurl to that list https://flurl.dev/. It's an amazing library and can be super helpful for quick one off API calls.
-
Anyone else be lost without notepad++
Linqpad for me, it's my go to scratch pad when testing out either new tech or edge cases and POCs than firing up a new console project. Especially when wanting to try out new nuget packages and see how they work. Even for messing with external apis I use it with Flurl, especially for apis that don't have any proper documentation.
- Api & Asp.net begginer question
-
What is the best practice to send query parameters / data on http client get method?
If you working with api use flurl You can also read source code on github.
-
Benchmarks Clients Http
Flurl:
Simple.OData.Client
We haven't tracked posts mentioning Simple.OData.Client yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
RestSharp - Simple REST and HTTP API Client for .NET
Refit - The automatic type-safe REST library for .NET Core, Xamarin and .NET. Heavily inspired by Square's Retrofit library, Refit turns your REST API into a live interface.
Polly - Polly is a .NET resilience and transient-fault-handling library that allows developers to express policies such as Retry, Circuit Breaker, Timeout, Bulkhead Isolation, and Fallback in a fluent and thread-safe manner. From version 6.0.1, Polly targets .NET Standard 1.1 and 2.0+.
Ocelot - .NET API Gateway
RestEase - Easy-to-use typesafe REST API client library for .NET Standard 1.1 and .NET Framework 4.5 and higher, which is simple and customisable. Inspired by Refit
FastEndpoints - A light-weight REST API development framework for ASP.Net 6 and newer. [Moved to: https://github.com/FastEndpoints/Library]
titanium-web-proxy - A cross-platform asynchronous HTTP(S) proxy server in C#.
Cashew - A simple and elegant yet powerful HTTP client cache for .NET