Traditional terminal emulators as they grew in the Windows environment also grew to allocate, typically, 4 megabytes of memory for each session opened. This is due to large class libraries or COM objects implemented to cover a broad set of functionality.
This slows-down the loading process as well as imposes severe resource requirements on each server running into gigabytes of memory.
With Flynet Viewer, each session is only an incremental area of memory (and some system handles) allocated. This brings-down the resource requirements for each session significantly to under 100K (if that).
Lower resource requirements not only enables faster initialization and execution of each session: it also enables a far lower server hardware requirement, both in CPU and memory. When a high-specification server IS implemented, with Flynet Viewer it runs that much faster.
