Function tor_dirclient::get_resource

pub async fn get_resource<CR, R, SP>(
    req: &CR, 
    dirinfo: DirInfo<'_>, 
    runtime: &SP, 
    circ_mgr: Arc<CircMgr<R>>
) -> Result<DirResponse> where
    CR: Requestable + ?Sized,
    R: Runtime,
    SP: SleepProvider, 

Fetch the resource described by req over the Tor network.

Circuits are built or found using circ_mgr, using paths constructed using dirinfo.

For more fine-grained control over the circuit and stream used, construct them yourself, and then call download instead.

TODO

This is the only function in this crate that knows about CircMgr and DirInfo. Perhaps this function should move up a level into DirMgr?