tinystruct-patterns

Topics in the source

• tinystruct Development Patterns
• Core Principle
• Primary Development Tool: bin/dispatcher
• Generating bin/dispatcher and bin/dispatcher.cmd
• When to Activate
• When to Use
• How It Works
• Examples

Architecture and implementation patterns for building modules with the tinystruct Java framework – a lightweight, high-performance framework that treats CLI and HTTP as equal citizens, requiring no main() method and minimal configuration. CLI and HTTP are equal citizens. A transport-neutral @Action uses Mode.DEFAULT (or omits mode) and has no HTTP-only dependencies. Such an action can run from both a terminal and a web browser. Mode.DEFAULT removes the transport restriction; it does not make an HTTP-dependent method CLI-compatible. Request and Response parameters come from HTTP context attributes and remain null when those attributes are absent, as in an ordinary CLI invocation. Keep shared logic independent of HTTP objects, sessions, and uploads, and call it from transport-specific entry points when needed. This "dual-mode" capability is the core design philosophy of tinystruct. An action with a transport-specific mode (Mode.CLI, Mode.HTTPGET, Mode.HTTPPOST, ...) is deliberately bound to that transport: the framework rejects it from the other one with "The action is not allowed to be executed." bin/dispatcher is the default, highest-priority tool for developing, running, testing,

This is an excerpt. Refer to the complete source and its current requirements.