Aloe Express Classes

This page provides information on the classes that make up the Aloe Express module.


CacheEngine is designed to make server-side caching easy and convenient. The cache itself is a Xojo.Core.Dictionary, and so in theory you can cache anything you'd like, from simple values and content to complex objects. Learn more >


Xojo uses a co-operative threading model, and as a result, all threads must run on a single core. To make use of other cores, Xojo suggests using separate processes in the form of "helper apps." The HelperApp class is designed to make implementing helper apps a little easier. Learn more >


The Logger class can be used to generate a log of requests and responses in the industry standard Extended Log File Format. It is primarily intended for use with Web site and app projects, so that traffic and usage can be analyzed. Learn more >


The Aloe Express server maintains a pool of Request class instances. When the server receives a request, it assigns it to an available Request instance. The class provides easy access to the request's headers, parameters, and more. Learn more >


To prevent long-running requests from blocking other requests, Aloe Express uses a multi-threaded model. When a Request is ready for processing, it is assigned to a RequestThread instance, which removes it from the main thread.


All requests are assigned an instance of the Response class. This class makes it easy for developers to specify all aspects of a response, including its status code, headers, and content. Learn more >


At the core of every Aloe Express-based app is an instance of the Server class. The Server listens on a specified port for incoming requests, and hands them off to a pool of Request instances. Learn more >


Aloe Express-based apps can be designed to listen on multiple ports, and the "ServerThread" helps to make this possible. Learn more >


For Web sites and apps that require sessions, Aloe Express provides SessionEngine. Each session is a Xojo.Core.Dictionary that has been assigned a unique ID. The engine handles all aspects of state management, including session expirations, assigning new IDs to prevent session fixation attacks, and more. Learn more >