Does Zend Http Client Provide a Graceful Cancellation API?

Goal

Gracefully abort HTTP requests in Zend Framework while respecting timeouts.

Current Constraints

The timeout option limits only socket read/write. No native cancel API exists. Adapter‑specific behavior: Curl honours timeout for the whole request, Socket may ignore DNS/redirects.

Unresolved Decision

Should the timeout encompass DNS resolution, redirects, and SSL handshakes? How to expose a cancellation method without breaking backward compatibility?

Open Questions

1. Which stages of the HTTP transaction should the timeout cover?
2. How can a cancellation API be integrated into Zend Http Client while preserving existing adapter contracts?
3. Does the current timeout behavior differ significantly between Curl and Socket adapters, and what impact does that have on user expectations?