Menu
Guide to selecting and configuring Horse server adapters (Indy console, CGI, ISAPI, Daemon, HTTP.sys).
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Guidelines and workflows for developing and maintaining regular expressions and optional parameter routing features in the Horse framework.
Guidelines for registering, executing, and optimizing native high-precision telemetry hooks (AddOnTelemetry) in the Horse Web Framework.
Guidelines for instantiating and configuring independent Horse server instances (THorseInstance) running concurrently on different ports.
Guide for setting up thread-safe database connection pooling (FireDAC / UniDAC) in multithreaded Horse applications.
Guide for managing request-scoped contextual services and IoC (dependency injection) in Delphi and Lazarus.
Guide to using standard Horse middlewares (CORS, Jhonson, compression, basic-auth, logger) and pipeline registration order.
| name | horse-providers |
| description | Guide to selecting and configuring Horse server adapters (Indy console, CGI, ISAPI, Daemon, HTTP.sys). |
Horse supports multiple execution providers. To change the provider, simply include the corresponding unit in your .dpr uses clause.
Horse.Provider.Console (Default - Indy-based): Launches a standalone console application listening on a TCP port. Best for local development and microservices.Horse.Provider.Daemon: Integrates Horse with Windows Services or Linux Daemons.Horse.Provider.HTTPsys: Integrates with the native Windows HTTP Server API (HTTP.sys). Provides high performance and native SSL/HTTPS support on Windows without needing Apache/Nginx.Horse.Provider.CGI / Horse.Provider.ISAPI: For deployment inside IIS (Internet Information Services) or Apache on Windows.Horse.Provider.Apache: Native Apache web server module.program MyAPI;
{$APPTYPE CONSOLE}
uses
// Include the target provider unit. Only ONE provider should be active.
Horse,
Horse.Provider.HTTPsys;
begin
THorse.Get('/health',
procedure(Req: THorseRequest; Res: THorseResponse; Next: TProc)
begin
Res.Send('healthy');
end);
// Starts the HTTPsys server
THorse.Listen(8080);
end.