And give up time to other threads. The RomPager software uses a single process thread or task with multiple TCP connections maintained in the TCP layer and multiple overlapping HTTP requests supported by the RomPager engine using internal request control blocks and a lightweight scheduler. If a message-passing model is used, messages are passed to the thread from the TCP interface for packet activity. The HTTP protocol is not very time sensitive, so the RomPager thread can be run at a low priority. Memory The Allegro RomPager engine and toolkit runtime routines take between 7KB to 30KB of ROM code with 4KB of ROM data, 1KB basic engine RAM, and 3KB to 5KB of RAM per simultaneous HTTP request.
Actual requirements depend on which compilation options and engine features are chosen.
The RomPager application toolkit uses several techniques to save page memory, including dynamic HTML generation and text pointer sharing. A typical application page and set and get routines will take between 25KB and 35KB of memory, depending on complexity and image use. When you are accessing a device that requires monitoring and control, such as a laser printer, an uninterruptible power supply, or building automation system, you want current information to make decisions on control. Usually, HTML pages are created in advance and sent to the client on request. For the Web server to provide current information, a new HTML page-generation method is required.