The request path.
WHAT HAPPENS
A request arrives at the web server It is passed to your application Your application produces a response It is returned to the visitor
WHAT SITS BETWEEN
An application server, which manages your application's processes and passes requests to it.
WHY THAT MATTERS
Your application does not handle the network directly.
WHAT YOUR APPLICATION MUST PROVIDE
An entry point the server can call: a callable object your framework provides.
WHAT THE STARTUP FILE IS
The file containing that entry point.
WHAT TO CONFIGURE
The startup file and the entry point name, in the application settings.
WHAT GOES WRONG MOST OFTEN
The entry point name not matching what the configuration expects.
WHAT THAT LOOKS LIKE
The application fails to start, and the log names the missing attribute.
WHAT ELSE TO UNDERSTAND
Your application runs as a persistent process, not per request.
WHAT THAT MEANS
State persists between requests, and code changes require a restart.
