Request Lifecycle
Requests in the Angel3 framework go through a relatively complex lifecycle, and to truly master the framework, one must understand that lifecycle.
  1. 1.
    startServer is called.
  2. 2.
    Each HttpRequest is sent through handleRequest.
  3. 3.
    handleRequest converts the HttpRequest to a RequestContext, and converts its HttpResponse into a ResponseContext.
  4. 4.
    angel3_route is used to match the request path to a list of request handlers.
  5. 5.
    Each handler is executed.
  6. 6.
    If the response is using streaming, and not buffering content, skip to step 8 (default).
  7. 7.
    All responseFinalizers are run.
  8. 8.
    If res.isDetached == false, all headers, the status code and the response buffer are sent through the actual HttpResponse.
  9. 9.
    The HttpResponse is closed.
If at any point an error occurs, Angel3 will catch it. See the error handling docs for more.

Next Up

Continue reading to learn about Dependency Injection.
Copy link
Contents
Next Up