developer-delphi-horse-orchestrator

A Horse orchestrator routes HTTP requests by acting as a single entry point for Delphi/FPC servers, analyzing context and delegating calls to specialized sub-skills. It coordinates middleware, routing, and safety checks to seamlessly dispatch requests to dedicated modular services.

The best way to manage Horse middleware like JWT and CORS is through a central orchestrator skill. It coordinates these safety checks and routing configurations, ensuring requests reach the correct specialized sub-skills within the Horse suite consistently.

Yes, you can use a Horse orchestrator as a single entry point to orchestrate ecosystem calls for Delphi and FPC. It routes HTTP Horse calls and delegates to specialized skills, enabling modular development and scalable server architecture.

To start routing HTTP Horse requests, run the orchestrator to analyze context and dispatch calls to the appropriate sub-skills within the Horse family. Ensure clear context and stable integration with Horse components to maintain consistent behavior.

No, the Horse orchestrator does not directly handle JWT authentication or Swagger documentation itself. It analyzes request context and routes calls to the appropriate specialized Horse skills that manage these specific middleware tasks.

You should not use a central orchestrator for Horse server routing if you lack clear context or stable integration with Horse components. The orchestrator requires these to maintain consistent behavior and properly delegate to specialized sub-skills.