Similarly to the IFFFS Wiretap server, the Wiretap Gateway uses a hierarchy of nodes to expose the structure of a public filesystem, intelligently presenting supported media as clips.
The gateway sever is a multi-process system that consists of 3 processes:
- The master process, launched at startup, dispatches calls to the other two processes.
- The session processes are created upon connection from client that maintain a consistent and isolated state for each client. They are tied to client process and all server handles created by a client process will use the same sessions.
- The slave processes are spawned by the master process on startup and are shared between session processes to offload image processing of high latency codec formats like red.
The Wiretap Gateway exposes the directories, clips and files of a filesystem. The following diagram shows a directory structure containing DPX, OpenEXR and RED raw image files, plus audio and a timeline in XML format.
The following diagram shows the same directories as seen through the Wiretap Gateway.
The following table presents the node types exposed through the Wiretap Gateway.
| Node Type | Description |
|---|---|
| NODE | Generic node type. Used mainly to contain directory (DIR) nodes. |
| DIR | DIR nodes are the first level below the root node of the server. |
| CLIP | A CLIP node exposes media in the form of frames.
For details, see Structure of a Wiretap Gatweay Server Clip Node. |
| HIRES | A HIRES node contains high-resolution video frames. |
| LOWRES | A LOWRES node contains low-resolution video frames.
Note: Only selected CLIP nodes have low-resolution representations. For example, RED (.r3d) CLIP nodes.
|
| AUDIOSTREAM | An AUDIOSTREAM node represents a block of audio media |