Lines 1-47
Link Here
|
1 |
--- Session.pm.orig Wed Jun 12 11:56:43 2002 |
|
|
2 |
+++ Session.pm Wed Jun 12 12:04:39 2002 |
3 |
@@ -915,7 +915,7 @@ |
4 |
=head2 STANDARD INSTALLATION |
5 |
|
6 |
The library is installed with just like other Perl libraries, or via CPAN interactive |
7 |
-shell (Perl -MCPAN -e install CGI::Session). |
8 |
+shell (Perl -MCPAN C<-e> install CGI::Session). |
9 |
|
10 |
Installation can also be done by following below instructions: |
11 |
|
12 |
@@ -1117,7 +1117,7 @@ |
13 |
above example. So, how do we "mark" the user? There are several ways of |
14 |
"marking". |
15 |
|
16 |
-=head3 IDENTIFYING THE USER VIA CGI QUERY |
17 |
+=item IDENTIFYING THE USER VIA CGI QUERY |
18 |
|
19 |
One way of doing it is to append the session id to every single link in the |
20 |
web site: |
21 |
@@ -1167,7 +1167,7 @@ |
22 |
session id appended to them. Too bad, because the client has to start |
23 |
everything over again. |
24 |
|
25 |
-=head3 INDENTIFYING THE USER VIA COOKIES |
26 |
+=item INDENTIFYING THE USER VIA COOKIES |
27 |
|
28 |
We can deal with the above problem by sending the client a cookie. This cookie |
29 |
will hold the session id only! Thus if the client visits some other site, or |
30 |
@@ -1211,7 +1211,7 @@ |
31 |
the C<sid> parameter in the URL, and if that fails, then it will default to |
32 |
undef, which will force C<CGI::Session> to create a new id for the client. |
33 |
|
34 |
-=head3 IDENTIFYING THE USER VIA PATH_INFO |
35 |
+=item IDENTIFYING THE USER VIA PATH_INFO |
36 |
|
37 |
The least common, but at the same time quite convenient way of C<marking> users |
38 |
with a session id is appending the session id to the url of the script |
39 |
@@ -1363,7 +1363,7 @@ |
40 |
|
41 |
=back |
42 |
|
43 |
-=head3 SPECIAL NAMES |
44 |
+=item SPECIAL NAMES |
45 |
|
46 |
When you create a fresh-blank session, it's not blank as it seems. It is |
47 |
initialized with the following 4 parameters, which are serialized together |