Commented global TODO list entries

Caching policy on the server

No policy exists that allows the server to check wheter a proxy is allowed to receive a certain video or not. The interfaces for such a policy are already included in the code but a policy is not implemented so far.

Some things have been changed

Several changes have been made to the code. For example, timers are now based on templates, which makes them considerably more flexible. Callback functions can be chosen arbitrarily. A minimal speed loss is the price.

Make losslists in MNRTPDecoderSH SSRC-dependent.

Separate losslists from MNRTPDecoderSH and put them into a separate SH. Update the GMs that use LC.

Do the same for MNRTPEncoderSH. Update the GMs that use LC.

Move RTP code documentation to the header and translate it to english.

Extract SDP and other content type code, put it into a separate subdirectory and into a separate namespace. Understand and document the content type selection. Verify that the interaction of RTSP/SDP and RTP code is correct.

Modify the client subsystem. Instead of forking a new process for the subsystem, keep a separate process from the beginning, and order that process through a pipe to fork the subsystem. In this way, speed is reduced because of the double indirection but reliability is increased because the communication process does not inherit any open files, specifically not X.

Separate RTSP and RTP parts. They should communication via pipes or UNIX-sockets. Use the same code that is used in the communication of client and client subsystem.

Implement RTSP containers.

Separate RTSP and RTP.

Generalize data pumps. This should make it easier to recover the VideoCharger code and also to add INSTANDE.

---