parent
68f4b2ec11
commit
04019d1b27
8 changed files with 90 additions and 8 deletions
@ -1 +1,11 @@ |
|||||||
# Odata |
# Odata |
||||||
|
|
||||||
|
OData (Open Data Protocol) is a web protocol for querying and updating data. It is an open standard for creating and consuming RESTful web services. OData is built on top of the HTTP protocol, and it uses the conventions of REST to expose data through a standard interface. |
||||||
|
|
||||||
|
In ASP.NET, OData can be used to create RESTful web services that expose data in a standardized way. OData provides a set of conventions for defining the structure of the data, and it also provides a set of conventions for querying and updating the data. |
||||||
|
|
||||||
|
For more information, visit the following links: |
||||||
|
|
||||||
|
- [Create an OData v4 Endpoint Using ASP.NET](https://learn.microsoft.com/en-us/aspnet/web-api/overview/odata-support-in-aspnet-web-api/odata-v4/create-an-odata-v4-endpoint) |
||||||
|
- [Working with OData in ASP.NET Core](https://www.pluralsight.com/blog/software-development/odata-asp-net-core) |
||||||
|
- [Example of OData Protocol With ASP.NET Core](https://www.youtube.com/watch?v=L9HdnNCi0R0) |
@ -1 +1,10 @@ |
|||||||
# Sieve |
# Sieve |
||||||
|
|
||||||
|
Sieve is a language for filtering email messages, it's defined in the Internet standard, also it's called as Sieve: An Email Filtering Language. It provides a simple, human-readable syntax for specifying rules that determine what actions to take on incoming email messages. These actions can include filing messages into different folders, forwarding messages to other addresses, discarding messages, and more. |
||||||
|
|
||||||
|
Sieve is typically used in email servers and clients, and it can be used to implement server-side and client-side email filtering. It allows users to create their own rules for filtering email, without requiring access to the server's configuration or the need for complex server-side scripts. |
||||||
|
|
||||||
|
To learn more, visit the following resources: |
||||||
|
|
||||||
|
- [Analysis of Sieve](https://en.wikipedia.org/wiki/Sieve_analysis) |
||||||
|
- [Sorting in a .NET Core API using Sieve](https://www.youtube.com/watch?v=x0utCah3cFk) |
@ -1 +1,11 @@ |
|||||||
# Rest |
# Rest |
||||||
|
|
||||||
|
REST (Representational State Transfer) is an architectural style for building web services. It is based on the principles of the HTTP protocol, and it uses the conventions of HTTP to create a standard interface for interacting with web services. |
||||||
|
|
||||||
|
In ASP.NET, REST can be used to create web services that expose data in a standardized way. RESTful web services in ASP.NET are typically built using the Web API framework, which provides a set of libraries and tools for building RESTful web services. |
||||||
|
|
||||||
|
To learn more, visit the following links: |
||||||
|
|
||||||
|
- [What is REST Services in ASP.NET?](http://www.codedigest.com/quick-start/16/what-is-rest-services-how-to-create-rest-services-in-aspnet) |
||||||
|
- [What are RESTful APIs?](https://www.pragimtech.com/blog/blazor/what-are-restful-apis/) |
||||||
|
- [Tutorial of Rest and Restful API](https://www.youtube.com/watch?v=4r1CIUs5s2I) |
@ -1 +1,11 @@ |
|||||||
# Grpc |
# GRPC |
||||||
|
|
||||||
|
gRPC is a high-performance, open-source framework for building remote procedure call (RPC) APIs. It uses the Protocol Buffers data serialization format and the HTTP/2 protocol to create highly efficient and scalable APIs. gRPC supports a variety of programming languages, including C# and ASP.NET. |
||||||
|
|
||||||
|
In ASP.NET, gRPC can be used to create high-performance, low-latency APIs for a variety of use cases. gRPC allows for bi-directional streaming of data, which can be useful for real-time applications such as gaming, financial trading, and more. |
||||||
|
|
||||||
|
To learn more, visit the following resources: |
||||||
|
|
||||||
|
- [Overview for gRPC on .NET](https://learn.microsoft.com/en-us/aspnet/core/grpc/?view=aspnetcore-7.0) |
||||||
|
- [Getting Started with ASP.NET Core and gRPC](https://blog.jetbrains.com/dotnet/2021/07/19/getting-started-with-asp-net-core-and-grpc/) |
||||||
|
- [Create a gRPC client & server in ASP.NET](https://learn.microsoft.com/en-us/aspnet/core/tutorials/grpc/grpc-start?view=aspnetcore-7.0&tabs=visual-studio) |
@ -1 +1,12 @@ |
|||||||
# Graphql dotnet |
# Graphql Dotnet |
||||||
|
|
||||||
|
GraphQL is a query language for your API, it allows clients to define the structure of the data they need, and the server will return only the requested data. It is an alternative to RESTful web services, and it is gaining popularity because of its flexibility and efficiency. |
||||||
|
|
||||||
|
In ASP.NET, GraphQL can be used to create web services that expose data in a more flexible and efficient way. GraphQL.NET is a popular open-source library that can be used to create GraphQL services in ASP.NET. This library provides a set of classes and methods that make it easy to create a GraphQL schema, handle requests, and generate responses. |
||||||
|
|
||||||
|
|
||||||
|
Learn more from the following resources: |
||||||
|
|
||||||
|
- [Introduction to Graphql Dotnet in ASP.NET](https://graphql-dotnet.github.io/docs/getting-started/introduction/) |
||||||
|
- [How to use GraphQL in .NET?](https://softchris.github.io/pages/dotnet-graphql.html) |
||||||
|
- [Building and consuming GraphQL API in ASP.NET](https://www.red-gate.com/simple-talk/development/dotnet-development/building-and-consuming-graphql-api-in-asp-net-core-5/) |
@ -1 +1,11 @@ |
|||||||
# Hot chocolate |
# Hot Chocolate |
||||||
|
|
||||||
|
Hot Chocolate is a GraphQL server implementation for .NET and .NET Core. It is an open-source library that provides a simple and flexible way to build GraphQL APIs in ASP.NET. |
||||||
|
|
||||||
|
Hot Chocolate provides a set of classes and methods that make it easy to create a GraphQL schema, handle requests, and generate responses. It also provides a number of features to help with things such as validation, authorization, caching, and more. |
||||||
|
|
||||||
|
To learn more, visit the following resources: |
||||||
|
|
||||||
|
- [Getting started with HotChocolate](https://learn.microsoft.com/en-us/shows/on-net/getting-started-with-hotchocolate) |
||||||
|
- [ASP.NET Core and HotChocolate](https://chillicream.com/docs/hotchocolate/v12/api-reference/aspnetcore) |
||||||
|
- [Intro to HotChocolate](https://chillicream.com/docs/hotchocolate) |
@ -1 +1,11 @@ |
|||||||
# Graphql |
# Graphql |
||||||
|
|
||||||
|
GraphQL is a query language for your API that allows clients to define the structure of the data they need, and the server will return only the requested data. It is an alternative to RESTful web services, and it is gaining popularity because of its flexibility and efficiency. |
||||||
|
|
||||||
|
In ASP.NET, GraphQL can be used to create web services that expose data in a more flexible and efficient way. There are several libraries available to implement GraphQL in an ASP.NET application, such as GraphQL.NET, Hot Chocolate, and others. These libraries provide a set of classes and methods that make it easy to create a GraphQL schema, handle requests, and generate responses. |
||||||
|
|
||||||
|
To learn more, visit the following resources: |
||||||
|
|
||||||
|
- [How to implement GraphQL in ASP.Net](https://blog.christian-schou.dk/how-to-implement-graphql-in-asp-net-core/) |
||||||
|
- [Intro to GraphQL](https://graphql-dotnet.github.io/docs/getting-started/introduction/) |
||||||
|
- [Developing API In .NET Core With GraphQL](https://www.c-sharpcorner.com/article/building-api-in-net-core-with-graphql2/) |
@ -1 +1,13 @@ |
|||||||
# Api clients |
# API Clients |
||||||
|
|
||||||
|
API clients in ASP.NET are software libraries that allow applications to interact with external APIs. They provide a set of methods and classes that make it easy to send requests to an API and process the responses. |
||||||
|
|
||||||
|
API clients can be used to access a wide variety of services, such as web services, cloud services, and social media platforms. They can be used to perform tasks such as fetching data, posting updates, and deleting resources. |
||||||
|
|
||||||
|
API clients in ASP.NET are typically built using the HttpClient class, which is part of the System.Net.Http namespace. This class provides a set of methods for sending HTTP requests and receiving HTTP responses. |
||||||
|
|
||||||
|
Visit the following links to learn more: |
||||||
|
|
||||||
|
- [How to Call a Web API From a .NET Client](https://learn.microsoft.com/en-us/aspnet/web-api/overview/advanced/calling-a-web-api-from-a-net-client) |
||||||
|
- [Overview of Web API REST Service in ASP.NET](https://www.c-sharpcorner.com/article/consuming-asp-net-web-api-rest-service-in-asp-net-mvc-using-http-client/) |
||||||
|
- [Building an ASP.NET Web API With ASP.NET](https://www.toptal.com/asp-dot-net/asp-net-web-api-tutorial) |
Loading…
Reference in new issue