Closes bug #22804 (moved phplib.session mention to a migration faq)

git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@124681 c90b9560-bf6c-de11-be94-00142212c4b1

faq/migration4.xml

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.8 $ -->
+<!-- $Revision: 1.9 $ -->
  <chapter id="faq.migration4">
   <title>Migrating from PHP 3 to PHP 4</title>
   <titleabbrev>Migrating from PHP 3 to PHP 4</titleabbrev>
@@ -29,6 +29,22 @@
      </para>
     </answer>
    </qandaentry>
+   
+   <qandaentry id="faq.migration4.sessions">
+    <question>
+     <para>
+      Do sessions work in PHP 3?
+     </para>
+    </question>
+    <answer>
+     <para>
+      Although <link linkend="ref.session">native session support</link>
+      didn't exist in PHP 3, there are third-party applications that did
+      (and still do) offer session functionality.  The most common method
+      was by using <ulink url="&url.phplib;">PHPLIB</ulink>.
+     </para>
+    </answer>
+   </qandaentry>
 
    <qandaentry id="faq.migration4.incompatible">
     <question>

reference/session/reference.xml

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.33 $ -->
+<!-- $Revision: 1.34 $ -->
  <reference id="ref.session">
   <title>Session handling functions</title>
   <titleabbrev>Sessions</titleabbrev>
@@ -13,11 +13,6 @@
      across subsequent accesses. This enables you to build more
      customized applications and increase the appeal of your web site.
     </para>
-    <para>
-     If you are familiar with the session management of PHPLIB, you
-     will notice that some concepts are similar to PHP's session
-     support.
-    </para>
     <para>
      A visitor accessing your web site is assigned an unique id, the
      so-called session id. This is either stored in a cookie on the