docs/pwg/advanced-request.xml: Fix 0.8 api usage in example. Fixes #554561

Original commit message from CVS:
* docs/pwg/advanced-request.xml:
Fix 0.8 api usage in example. Fixes #554561
* docs/pwg/appendix-porting.xml:
Change 0.9 to 0.10 here.

ChangeLog

@@ -1,3 +1,11 @@
+2008-10-06  Stefan Kost  <ensonic@users.sf.net>
+
+	* docs/pwg/advanced-request.xml:
+	  Fix 0.8 api usage in example. Fixes #554561
+
+	* docs/pwg/appendix-porting.xml:
+	  Change 0.9 to 0.10 here.
+
 2008-10-06  Stefan Kost  <ensonic@users.sf.net>
 
 	* docs/manual/basics-data.xml:

docs/pwg/advanced-request.xml

@@ -253,7 +253,7 @@ gst_my_filter_request_new_pad (GstElement     *element,
 
   context = g_new0 (GstMyFilterInputContext, 1);
   pad = gst_pad_new_from_template (templ, name);
-  gst_element_set_private_data (pad, context);
+  gst_pad_set_element_private (pad, context);
 
   /* normally, you would set _link () and _getcaps () functions here */
 

docs/pwg/appendix-porting.xml

@@ -1,13 +1,13 @@
 <chapter id="chapter-porting">
-  <title>Porting 0.8 plug-ins to 0.9</title>
+  <title>Porting 0.8 plug-ins to 0.10</title>
   <para>
     This section of the appendix will discuss shortly what changes to
     plugins will be needed to quickly and conveniently port most
-    applications from &GStreamer;-0.8 to &GStreamer;-0.9, with references
+    applications from &GStreamer;-0.8 to &GStreamer;-0.10, with references
     to the relevant sections in this Plugin Writer's Guide where needed.
     With this list, it should be possible to port most plugins to
-    &GStreamer;-0.9 in less than a day. Exceptions are elements that will
+    &GStreamer;-0.10 in less than a day. Exceptions are elements that will
-    require a base class in 0.9 (sources, sinks), in which case it may take
+    require a base class in 0.10 (sources, sinks), in which case it may take
     a lot longer, depending on the coder's skills (however, when using the
     <classname>GstBaseSink</classname> and <classname>GstBaseSrc</classname>
     base-classes, it shouldn't be all too bad), and elements requiring
@@ -21,15 +21,15 @@
     <itemizedlist>
       <listitem>
         <para>
-        Discont events have been replaced by newsegment events. In 0.9, it is
+        Discont events have been replaced by newsegment events. In 0.10, it is
         essential that you send a newsegment event downstream before you send 
         your first buffer (in 0.8 the scheduler would invent discont events if
-        you forgot them, in 0.9 this is no longer the case).
+        you forgot them, in 0.10 this is no longer the case).
         </para>
       </listitem>
       <listitem>
         <para>
-        In 0.9, buffers have caps attached to them. Elements should allocate
+        In 0.10, buffers have caps attached to them. Elements should allocate
         new buffers with <function>gst_pad_alloc_buffer ()</function>. See
         <xref linkend="chapter-negotiation"/> for more details.
         </para>
@@ -57,7 +57,7 @@
           be <function>_get ()</function>-based or <function>_loop
           ()</function>-based, and any other element could be  <function>_chain
           ()</function>-based or <function>_loop ()</function>-based, with
-          no limitations. Scheduling in 0.9 is simpler for the scheduler,
+          no limitations. Scheduling in 0.10 is simpler for the scheduler,
           and the element is expected to do some more work. Pads get
           assigned a scheduling mode, based on which they can either
           operate in random access-mode, in pipeline driving mode or in
@@ -78,7 +78,7 @@
       <listitem>
         <para>
           For as far as possible, elements should try to use existing base
-          classes in 0.9. Sink and source elements, for example, could derive
+          classes in 0.10. Sink and source elements, for example, could derive
           from <classname>GstBaseSrc</classname> and
           <classname>GstBaseSink</classname>. Audio sinks or sources could even
           derive from audio-specific base classes. All existing base classes
@@ -88,7 +88,7 @@
       </listitem>
       <listitem>
         <para>
-          In 0.9, event handling and buffers are separated once again. This
+          In 0.10, event handling and buffers are separated once again. This
           means that in order to receive events, one no longer has to set the
           <classname>GST_FLAG_EVENT_AWARE</classname> flag, but can simply
           set an event handling function on the element's sinkpad(s), using