The Wheat server doesn't have to map the entire object tree to the public URI space. In fact, like Apache, there is a mapping layer that allows various parts of the object tree to be mapped into different parts of the URI space.

Modules define how a request is handled. Modules combined with mapping allow the Wheat server to support different modes of use.

In the example at left:

Implementation note: While the server is just talking to the object tree, and knows nothing about object media, there is a clever path through the code: When mod_file asks for a file's byte stream contents, and it turns out that that the file object is actually a host file mounted via the host file object media, then the server ends up with a stream handler reading right from the file. So static content, like images, get streamed from the disk to the network without overhead.