[Feature] Access to Abort Signal from Client

[Kakapio]

I would like to have access to Abort Signal from the client implementation. We need access to it for some existing functionality we are looking to replace with reqwest.

cloudflare/workers-rs#510 (comment)

[seanmonstar]

Is the actual signal needed? I try to present a unified API in reqwest, without exposing internals. The signal is used to make the Drop behavior of the future the same as in non-wasm environments.

Can you do what you want without direct access?

[Kakapio]

Ah, I think we may be able to use Drop. Correct me if I'm wrong, since I'm new to Reqwest, but we could just have a handler for the functionality and pass it through like so:

// Asynchronous loop to continuously check for cancellation signal
    loop {
        tokio::select! {
            _ = sleep(Duration::from_secs(1)) => {
                println!("Async task running...");
            }
            _ = cancel_receiver.recv() => {
                println!("Cancellation signal received. Dropping task...");
                break; // Break out of the loop when cancellation signal is received
            }
        }
    }

[seanmonstar]

I believe that should do it.