We currently only cover the Recalls, and we still need to start the threads.

intended for protyping.
Retyped DiskWriteThreadPool's members to fixed length types.

MemBlock, MemManager, MemManagerClient, MigrationJob,
TapeReadFileTask, TapeReadTask, TapeSingleThreadInterface,
TapeReadSingleThread, TapeWriteTask, TaskInjector
into castor::tape::tapeserver::daemon

ClientInterface gained reportMigrationResults,reportEndOfSession(WithError) and VolumeInfod moved also to ClientInterface

RecallJob has been substituted by FileToRecallStruct and MockTapeGateaway by ClientInterface

The test and mount session have been adapted to the previous developments.
Mount session now goes as far as opening the tape drive.

This options allows us to prepare the contents of a drive for a unit test.
This function is only implemented for the fake systems and the drives of type VIRTUAL, so it is only available
for test environments.

Replaced the ad-hoc container castor::tape::drives::Drive by a factory function castor::tape::drives::DriveFactory.

Adapted the use in all the tests (with auto_ptr).

We need to make sure the coverage of the UT is enough

It now uses interfaces' types (TapeSingleThreadInterface<>, ClientInterface, and DiskThreadPoolInterface<>)instead of the types of the derived classes for its arguments

Thus the RecallTaskInjectorTest.cpp does not complain about link error

Indeed, there was a clash into auto_ptr destructor (which does a delete) and the allocation which was done using new[]

Added explaination for more bare dynamic casts to reference. Also added
cast to void for the result (to prevent compilation errors).

Added explaination for a bare dynamic cast to reference, which is not to
straightforward.

does not compile yet

Also removed the nested Worker class to make the interface inheriting from Thread

and refactor a bit of code into the interface