Frequently Asked Questions

Not at the moment. For now, if you need an AOT distribution, consider using the traditional ASP.NET Core minimal API.

Netiqo Framework requires .NET 9.0 or higher. This ensures you have access to the latest performance improvements and security features.

We specifically target .NET 9.0+ to take advantage of:

• Improved HTTP/2 and HTTP/3 support
• Enhanced performance in networking stack
• Better memory management
• Native JSON serialization improvements

Yes (subject to limitations, read the license), Netiqo Framework is designed for production use, particularly for embedded applications, microservices, and local network services.

However, for high-traffic public web applications, we recommend thorough testing and monitoring. The framework excels in scenarios like:

• IoT device web interfaces
• Local network APIs
• Desktop application web servers
• Microservices with controlled traffic

Netiqo Framework provides native HTTPS support using PFX certificate files. Here's how to configure it:

Make sure your PFX file contains both the certificate and private key. You can generate a self-signed certificate.

Direct Let's Encrypt integration is planned for a future release. Currently, you can use Let's Encrypt certificates by converting them to PFX format manually.

To use Let's Encrypt certificates with Netiqo Framework:

1. Obtain certificates using Certbot or similar tools
2. Convert PEM files to PFX format using OpenSSL
3. Configure Netiqo with the PFX file

Automatic renewal and management of certificates will be available in future versions.

Netiqo Framework supports multiple routing approaches for maximum flexibility:

• Manual Registration: Programmatically register routes in code
• JSON Configuration: Define routes in external JSON files
• XML Configuration: Use XML files for route definitions
• Attribute-based: Use [Route] attributes on controller methods

All methods support GET, POST, PUT, DELETE, and other HTTP verbs, with custom response handlers and parameter parsing.

Yes, Netiqo Framework supports data extraction without any kind of blocking. This is made possible by the following example code

  [Route("/login", Request.HttpMethod.POST)]
        public string HandleLogin(string body)
        {
            var parsed = System.Web.HttpUtility.ParseQueryString(body);
            string user = parsed["username"];
            string pass = parsed["password"];
            return $"Welcome, {user}!";
        }

Netiqo Framework automatically serves static files from the wwwroot/ directory in your application folder. This includes CSS, JavaScript, images, and other assets.

Features include:

• Automatic MIME type detection
• Efficient file streaming for large files
• Built-in caching headers
• Directory browsing (optional)

No additional configuration required - just place your files in the wwwroot folder and they'll be accessible via HTTP.

Netiqo Framework is optimized for lightweight scenarios and typically shows:

• Lower memory footprint: 60-80% less RAM usage for basic scenarios
• Faster startup time: 3-5x faster cold start
• Comparable throughput: Similar RPS for small to medium loads

However, for high-concurrency scenarios (1000+ concurrent connections), ASP.NET Core's Kestrel server will generally outperform Netiqo due to more advanced pooling and optimization strategies.

Netiqo excels in embedded scenarios, IoT applications, and situations where minimal resource usage is critical.