buffer: improve the buffer memory methods

gst_buffer_take_memory -> gst_buffer_insert_memory because insert is what the
method does.
Make all methods deal with ranges so that we can replace, merge, remove and map
a certain subset of the memory in a buffer. With the new methods we can make
some code nicer and reuse more code. Being able to deal with a subset of the
buffer memory allows us to optimize more cases later (most notably RTP headers
and payload that could be in different memory objects).
Make some more convenient macros that call the more generic range methods.

1 files changed, 1 insertions, 1 deletions

diff --git a/docs/random/porting-to-0.11.txt b/docs/random/porting-to-0.11.txt
index 9a1642b9d..0b9bd38a2 100644
--- a/docs/random/porting-to-0.11.txt
+++ b/docs/random/porting-to-0.11.txt
@@ -203,7 +203,7 @@ The 0.11 porting guide
     A GstBuffer is now a simple boxed type this means that subclassing is not
     possible anymore. 
 
-    To add data to the buffer you would now use gst_buffer_take_memory() with
+    To add data to the buffer you would now use gst_buffer_insert_memory() with
     a GstMemory object containing the data. Multiple memory blocks can added to
     a GstBuffer that can then be retrieved with gst_buffer_peek_memory().