- Moved cRecordings locking infrastructure to RecordingsManager.

- Take care to have at any time maximum one instance of RecordingsManager
  alive. This is done with a combination of boost::shared_ptr and
  boost::weak_ptr. See LiveRecordingsManager() function.
- RecordingsTree now uses RecordingsManager to calculate a MD5 Hash for
  each 'real' cRecording item.
- The MD5 Hash is used in the Ajax-Request to start play back of a
  recording. (Server side needs implementation of this.)
- Id's are also used in the DOM for the identification of the tooltips.
- New code dependency on openssl libraries (for md5 function).
- Changed style (not yet complete) to have 'action' items also in the
  recording description popup.

0 files changed, 0 insertions, 0 deletions