From 2b09d7f121ca08d377575364f8ef25ac7a6bcb50 Mon Sep 17 00:00:00 2001 From: Michael Wallner Date: Wed, 3 Feb 2016 17:22:39 +0100 Subject: [PATCH] style and wording fixes --- http/Client/enqueue.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/http/Client/enqueue.md b/http/Client/enqueue.md index 1214996..a863710 100644 --- a/http/Client/enqueue.md +++ b/http/Client/enqueue.md @@ -3,8 +3,13 @@ Add another http\Client\Request to the request queue. If the optional callback $cb returns true, the request will be automatically dequeued. -> ***Note:*** -> The http\Client\Response object resulting from the request is always stored in an internal storage, __even__ when callback is used, because of that, the memory may grow up significantly if you send many many requests using the same http\Client instance... In that case, to keep memory as low as possible, it is advised to call http\Client::getResponse() in the callback or to call http\Client::reset() after each http\Client::send() to free some ressources. +> ***Note:*** +> The http\Client\Response object resulting from the request is always stored +> internally to be retreived at a later time, __even__ when $cb is used. +> +> If you are about to send a lot of requests and do __not__ need the response +> after executing the callback, you can use http\Client::getResponse() within +> the callback to keep the memory usage level as low as possible. See http\Client::dequeue() and http\Client::send(). -- 2.30.2