… | |
… | |
221 | This callback is useful when the data is too large to be held in memory |
221 | This callback is useful when the data is too large to be held in memory |
222 | (so the callback writes it to a file) or when only some information should |
222 | (so the callback writes it to a file) or when only some information should |
223 | be extracted, or when the body should be processed incrementally. |
223 | be extracted, or when the body should be processed incrementally. |
224 | |
224 | |
225 | It is usually preferred over doing your own body handling via |
225 | It is usually preferred over doing your own body handling via |
226 | C<want_body_handle>. |
226 | C<want_body_handle>, but in case of streaming APIs, where HTTP is |
|
|
227 | only used to create a connection, C<want_body_handle> is the better |
|
|
228 | alternative, as it allows you to install your own event handler, reducing |
|
|
229 | resource usage. |
227 | |
230 | |
228 | =item want_body_handle => $enable |
231 | =item want_body_handle => $enable |
229 | |
232 | |
230 | When enabled (default is disabled), the behaviour of AnyEvent::HTTP |
233 | When enabled (default is disabled), the behaviour of AnyEvent::HTTP |
231 | changes considerably: after parsing the headers, and instead of |
234 | changes considerably: after parsing the headers, and instead of |
… | |
… | |
243 | This is useful with some push-type services, where, after the initial |
246 | This is useful with some push-type services, where, after the initial |
244 | headers, an interactive protocol is used (typical example would be the |
247 | headers, an interactive protocol is used (typical example would be the |
245 | push-style twitter API which starts a JSON/XML stream). |
248 | push-style twitter API which starts a JSON/XML stream). |
246 | |
249 | |
247 | If you think you need this, first have a look at C<on_body>, to see if |
250 | If you think you need this, first have a look at C<on_body>, to see if |
248 | that doesn'T solve your problem in a better way. |
251 | that doesn't solve your problem in a better way. |
249 | |
252 | |
250 | =back |
253 | =back |
251 | |
254 | |
252 | Example: make a simple HTTP GET request for http://www.nethype.de/ |
255 | Example: make a simple HTTP GET request for http://www.nethype.de/ |
253 | |
256 | |