because Open Source works.
The TinyX is a collection of X11 servers targetted for environments where non-volatile file system space is limited. This means that size of the executables is small, and the runtime dependency on other filesis minimised.
The RAM requirements of the TinyX servers is highly dependent on the applications.
For applications with significant server-side resource usage, the RAM requirements may not be much differentthan for the regular XFree86 servers.
There is a memory usage benefit for applications with low server-side resource usage.
Up until now it hasn't been possible to build the XFree86 and TinyX servers at the same time.
The differences in build options for the device-independent X server components meant that separate build configuration settings were required for each server.
There are two classes of differences between the main X Server and TinyX:
The first classes concerns highly modular components, such as font renders and modular X server extensions. This is a minor issue as they can easily be disabled on a per-X server basis.
The second class is a more substantive change as it includes less modular components, such as X server extensions themselves. This is not as straight forward because of the way thhat they are implemented in the server.Some examples of these are the XINPUT, XKEYBOARD, and LBX extensions.
The problem therein becomes that to disable these second class of of extensions for only some X servers in a build requires building two copies of some components: a standard fully featured copy, and a "tiny" copy with the unneeded features disabled.
We did not want to do that naturally so it meant extensive reworking of the build options for a true standalone TinyX.
.BENEFITS of the new TinyX are:
- Ensuring that both servers are updated along with the main XFree86 server when there are interface changes.
- Resolving the differences between the two DDX models has led to improvements in the non-DDX areas of the X server code.
- Allowing requirements for both types of configurations to be satisified via run-time selection of components rather than build-time selection.
- Identifying areas of the non-DDX code that have poor modularity.
- Understanding of the requirement differences between the XFree86 server and the TinyX servers
If you would like to deploy TinyX, contact us to discuss how best to adapt TinyX to your environment.
We would also like to hear about situations where the standalone TinyX is working for you
copyright 2014 x-oz.com.
All rights reserved.