Download to read offline
Uploaded byNgoc Dao
Xitrum internals
Xitrum uses the Netty framework and follows a handler-based architecture. It aggregates HTTP requests and responses into a HandlerEnv object that passes through various handlers. These handlers include converting requests to HandlerEnv, selecting and calling actions, converting responses back to HTTP, and more. Routing is done by collecting routes specified by annotations at startup and dispatching requests to the appropriate action class execute method.
Xitrum internals
- 1.
- 2. Handler architecture based onNetty 4 Request (Inbound) Response (Outbound) ServerSsl Aggregates HttpObjects (headers and contents) to make Xitrum HandlerEnv; all Xitrum handlers work with HandlerEnv Request2Env ChunkedWrite NoPipelining Env2Response SetCORS BasicAuth OPTIONSResponse PublicFileServer FixiOS6SafariPOST PublicResourceServer Serves resource files in classpath (and JAR files) HttpResponseEncoder BaseUrlRemover Serves static files in public directory HttpRequestDecoder XSendFile UriParser XSendResource MethodOverrider Selects and calls action (see next slide) Converts Xitrum HandlerEnv to Netty’s FullHttpResponse Shortcut may happen (action will not be called at Dispatcher) ResponseCacher Dispatcher BadClientSilencer Catches all errors These 4 handlers are provided by Netty; the others are created by Xitrum Action#execute respondText, respondVi ew, respondFile, respondBinary etc.
- 3. Routing • Route collection: Atstartup, Xitrum automatically collects all routes specified by annotations @GET(“hello”), @POST(“hi”) etc. • Routing: At “Dispatcher” (see previous slide), the an instance of the specified action class is created and its “execute” method is called.