The information provided in response to a XrdCl::Query command is in the form of a
    string which represents the list of transfers and each transfer is a tuple having
    the following structure:
	(tident,castor_path,tx_type,isRW,ReqId)
    - tident contains: userid.procid:fd@client_host
    - castor_path is the physical path to the file as represented in the CASTOR world
    - tx_type can have one of the following values: user, tape, d2duser, d2dbalance,
      d2dinternal, d2ddrain or unknown. This is easily extensible as whatever is
      received in the opaque information with the tag "castor.txtype" is returned at
      this stage
    - 0 for read operations 1 for write operations
    - ReqId - request id in case of user initiated transfers i.e. transfers that go
      through the XRootD headnode and will be 0 for all the rest of the transfers that
      don't have a request id