READ ALSO: Image Variants in Web Applications READ ALSO: Images in Web Applications READ ALSO: Brief History of Images in Software In the early history of the Web, GIF was the first widely used image format. Short for Graphics Interchange Format, it was introduced by CompuServe in 1987, well before JPEG became practical for theContinue reading “Browsing for Images”
Category Archives: Web
Brief History of Images in Software
READ ALSO: Image Variants in Web Applications READ ALSO: Images in Web Applications Today the acronym JPEG is so popular to be rightfully considered a synonym to the same term image. Yet there was a time—and not even that many years ago—in which computer science progressed without it. Let’s start with a brief history ofContinue reading “Brief History of Images in Software”
Dealing with Business Images with Variants
READ ALSO: Images in Web Applications Speaking of images in web applications, an additional point to consider—beyond choosing the most effective storage medium—is how to deal with multiple variants of the same image that may need to be stored and served. If, in general terms, storage can be one of a few options—database, file system,Continue reading “Dealing with Business Images with Variants”
Handling Business Images in Web Applications
READ ALSO: Image Variants in Web Applications Across the millennium, a technical article explaining step by step how to save an image to—and read it from—a database column as a plain array of bytes was pure gold. At the time, images were almost invariably treated as separate files deployed in some folder on the webContinue reading “Handling Business Images in Web Applications “
Inside async/await in C#
C# introduced the async/await feature in 2012 to simplify asynchronous programming, which was previously convoluted and error-prone. The compiler transforms async methods into state machines, allowing for non-blocking execution while maintaining a sequential code appearance. This innovation enhances code readability and optimizes resource management in both desktop and web applications.
Returning ZIP Files and Hypermedia in Minimal APIs
Minimal APIs in ASP.NET Core provide built-in results like Results.Ok(), but custom IResult implementations are essential for returning unique content types such as ZIP files or hypermedia responses. Custom IResult grants control over headers, serialization, and content types, allowing developers to handle complex data responses effectively and maintain clean endpoint code.
Results and Metadata in Minimal APIs
The Minimal API framework in ASP.NET Core simplifies HTTP API development, using IResult and ITypedResult for responses. IResult is fundamental for various API outputs, while ITypedResult enhances metadata for tools like Swagger. Developers typically use static Results methods for endpoint responses, with Produces() aiding in complex scenarios where inference fails.
Timing Minimal APIs vs Controllers
ASP.NET Core developers can choose between Minimal APIs and traditional MVC controllers, each offering unique structure and performance implications. This analysis highlights the request lifecycle differences and performance benchmarks. Generally, Minimal APIs are slightly faster, though real-world conditions often diminish the timing significance. Code organization also varies, with MVC providing inherent structure.
How the ASP.NET Runtime Works – part 2
This content outlines the request pipeline in an ASP.NET Core application, detailing its construction from the initial application builder through to the execution of requests. The process includes building and configuring middleware, managing endpoints, and handling requests with various delegate types. The final transition to live execution occurs upon calling Run, finalizing the pipeline.
How the ASP.NET Runtime Works – part 1
This article describes the startup process of an ASP.NET Core application, focusing on the WebApplication.CreateBuilder method that initializes the web host, configuration, dependency injection, and logging. It highlights server options like Kestrel and HTTP.sys, and the role of reverse proxies such as IIS, Nginx, and Apache in managing HTTP requests.
