Found 9 packages
Make ASP.NET MVC controllers and actions optional.
Custom ApiExplorer for genrating API documentation for message based apis.
SwiftApi: Turn service interfaces into fully functional API endpoints without writing controllers.
The Throttling Suite provides throttling control capabilities to the .NET Web API applications. It is highly customizable product, yet simple to use. The implementation supports all available hosting options provisioning equal functionality for IIS-hosted and OWIN self-hosted solutions. It is specifically designed to throttle high performance and high throughput Web API applications. The library contains multiple controller types implementing different throttling algorithms: Linear throttling - limits the number of calls by enforcing consistent delay between consequent requests; Short Average - limits the number of calls by specified number of requests per configured duration; it does not intend to limit the overall number of requests, but rather assures blocking excessive requests; this strategy is very helpful to cut the requests floods; Long Average - limits the number of calls by specified number of requests per configured duration; this strategy limits an overall number of calls within long time duration; this is also known as applying penalty to the client for excessive application use. Each throttling controller is capable of unique client determination and management. The throttling for any end-point, or set of end-points can be configured either for the entire application, or per-client. It does not purely rely on client IP address, allowing multiple clients from the same network concurrently making requests to the server. The Throttling Suite allows setting multiple controllers within the application and applying each to a pre-filtered traffic. The filters are also configurable. The Throttling Suite provides two modes: real blocking mode when request is blocked with 429 HTTP Status code and log-only mode. The code is highly optimized having very low memory impact. The throttling evaluation functionality takes less than 0.3 ms to run. The v1.2 is updated to include "Retry-After" response header in the blocked response helping API client to negotiate the request rate with API server side. The v1.2 also allows to ignore the actual request URL substituting one with Throttling controller instance scope. This provides the benefit to count requests for multiple API endpoints toward the same throttling threshold. The v1.3 enables configuration from the code rather than XML *.config file.
this library is to avoid wasting time with interface, service and controller connections and to write faster and less tedious code. Enable the UseUML() extension method by writing "app.UseUML()" in Program.cs, run the program once to create a UML controller. Since the UML controller is created at runtime, you can't use it in this case, then restart the program and send a request to "UMLController" with the Get protocol, and then enter the data into the console as shown below. Before reading the instructions, I would like to say that this library accepts and writes every line you write, so when sending data, follow the rules of writing an interface. Enter the interface information line by line without using \";\". Only methods starting with [HttpGet/...] are created in the controller. When finished, type \"yes\" in the console and press Enter. Example : [HttpGet] public IActionResult GetStudents() Good luck C# dude.
Enhance your ASP.NET Web API projects with this robust and easy-to-use library that provides a generic repository and controller for seamless CRUD operations. This package is designed to simplify the development process by offering out-of-the-box implementation of basic Create, Read, Update, and Delete (CRUD) functionalities, allowing developers to focus more on business logic and less on boilerplate code
The `Telegram` module provides a reactive, controller-less engine for integrating the Telegram messaging platform with XAF applications.
The `Workflow` module provides a reactive, controller-less engine for orchestrating complex, long-running, and scheduled business processes.
The library contains multiple controller types implementing different throttling strategies: Linear throttling - limits the number of calls by enforcing specified delay between consequent requests; Short Average - limits the number of calls by specified number of requests per configured duration; it does not limit overall number of requests, but rather assures blocking excessive requests; this strategy is very helpful to cut the requests flooding caused by such user behaviors as multi-click or hard click on F5 button; Long Average - limits the number of calls by specified number of requests per configured duration; this strategy limits an overall number of calls within long time duration; this is also known as applying penalty to the client for excessive application use. Each throttling controller uniquely determines the client making requests. It does not purely rely on client IP address allowing multiple clients from the same network concurrently making requests to the IIS. The Throttling Suite allows setting multiple controllers within the application and applying each to a pre-filtered traffic. The filters are also configurable. The Throttling Suite provides two modes: real blocking mode when request is blocked with 429 HTTP Status code and log-only mode whether it logs blocking information to IIS log, but allows request to continue. The log-only mode is very useful when there is a need to determine the most appropriate throttling configuration parameters. The code is highly optimized having very low memory impact and taking less than 0.3 ms to run on a regular development laptop. As an extra functionality it provides with real-time snapshot of current throttling status for all controllers. The snap-shot is available online as a JSON output. It requires configuration to assure authorized used as desired by an application.