The Manager

This is a new technic developed during three past years.

This technic is used in most of the Trakians.

Managers are simply small pieces of softwares completely independant from others and capable to take in charge their task and all what it requires. They can also communicate with others, sending or receiving 'messages'. But they can also start a classic program or function. And another function can also call them like a classic program.

And many collaborates in a program like the Trakian. You can have IO managers, protocole managers, file managers, timer managers, ...... and a lot of other.

Some are the kernel. Or the keyboard else the timer. And everyone being selfsufficient, he just 'do his job' for others.

Like the memory manager, a central one. He manages all the memory of the application or system and gives to other what they request. But he has also in charge to take the memory back when not needed and to collect small parts of the memory in larger areas.

Another important is the windowing system. Because this is what the user sees. And this is used by many programs.

A manager has another very important capability: he can disappear, release the memory space used and reload himself when required, for example when receiving a message from another. This is done by a small code which resides permanently in memory. So a manager is ALLWAYS present! But he can be active or inactive. The main differences from other technics is the size and the speed. Because a manager can reduce to about 100 bytes.

Many kinds of managers exist in a program like Trakian. And many others are not present because not needed. For example some manager is capable to manage a library of files, thousands of files in a one piece big file as seen by the system.

Trakian himself is simply a manager. The difference being that he manages ..... managers.

All of this makes that Trakian is small but also that he can run in a very small memory space. Because in fact many managers are not needed allways. And they liberate their space when not needed. For example, if Trakian is not active on the communication line, those in charge of the communication can simply 'disappear'.

You can see that many descriptions are also used for 'Operating systems' 'Multitask O.S.' In fact this is real: The manager's assembly create a multitask OS. But fast and code efficient .... because this technic render programs small!

JP Jacobs