diff options
| author | Patrick Griffis <pgriffis@igalia.com> | 2020-02-12 13:52:09 -0800 |
|---|---|---|
| committer | Patrick Griffis <pgriffis@igalia.com> | 2020-09-19 15:41:24 -0700 |
| commit | ddfb66b49f3cc38f51588aa07236b460bc0bba6f (patch) | |
| tree | 1c5d3f7014796a492d3a761c6a37112ae4106b9a /libsoup/soup-message-body.c | |
| parent | 86a10a2618473624d150dabbd449f41a6e28bf76 (diff) | |
| download | libsoup-ddfb66b49f3cc38f51588aa07236b460bc0bba6f.tar.gz | |
Remove deprecated SoupMessageBody API
Diffstat (limited to 'libsoup/soup-message-body.c')
| -rw-r--r-- | libsoup/soup-message-body.c | 5 |
1 files changed, 1 insertions, 4 deletions
diff --git a/libsoup/soup-message-body.c b/libsoup/soup-message-body.c index 0c45e18e..eb6d5f5a 100644 --- a/libsoup/soup-message-body.c +++ b/libsoup/soup-message-body.c @@ -351,8 +351,7 @@ G_DEFINE_BOXED_TYPE (SoupBuffer, soup_buffer, soup_buffer_copy, soup_buffer_free * message body, @data is normally %NULL, and will only be filled in * after soup_message_body_flatten() is called. For client-side * messages, this automatically happens for the response body after it - * has been fully read, unless you set the - * %SOUP_MESSAGE_OVERWRITE_CHUNKS flags. Likewise, for server-side + * has been fully read. Likewise, for server-side * messages, the request body is automatically filled in after being * read. * @@ -404,8 +403,6 @@ soup_message_body_new (void) * client-side message, or #SoupMessage:request_body of a server-side * message), this will cause each chunk of the body to be discarded * after its corresponding #SoupMessage::got_chunk signal is emitted. - * (This is equivalent to setting the deprecated - * %SOUP_MESSAGE_OVERWRITE_CHUNKS flag on the message.) * * If you set this flag to %FALSE on the #SoupMessage:response_body of * a server-side message, it will cause each chunk of the body to be |