From: Hu Hailin Date: Sat, 24 Mar 2007 19:40:30 +0000 (+0000) Subject: a typo and a link fixed X-Git-Tag: v0.15~7 X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=2cf2efb9a930c4433982f4f15cbdfc5b9850ceef;p=catagits%2FCatalyst-Plugin-Session.git a typo and a link fixed --- diff --git a/lib/Catalyst/Plugin/Session/Tutorial.pod b/lib/Catalyst/Plugin/Session/Tutorial.pod index 679ba46..22fff28 100644 --- a/lib/Catalyst/Plugin/Session/Tutorial.pod +++ b/lib/Catalyst/Plugin/Session/Tutorial.pod @@ -35,7 +35,7 @@ HTTP has a feature that lets this become easier, called cookies. A cookie is something the server asks the client to save somewhere, and resend every time a request is made. -They way they work is that the server sends the C header, with a +The way they work is that the server sends the C header, with a cookie name, a value, and some meta data (like when it expires, what paths it applies to, etc). The client saves this. @@ -99,7 +99,7 @@ application: This loads the session API, as well as the required backends of your choice. After the plugins are loaded they need to be configured. This is done according -to L. +to L. Each backend plugin requires it's own configuration options (with most plugins providing sensible defaults). The session API itself also has configurable