lockdown 0.4.4 → 0.4.5

data/History.txt

@@ -1,3 +1,6 @@
+== 0.4.5 2008-05-08
+* Rubyforge having an issue with the gem, I'm getting 404 errors trying to install 0.4.4 so I'm deploying a new version. no code changes.
+
 == 0.4.4 2008-05-08
 * Modified: refactored the link_to_secured and authorized? code to be more efficient
 

data/lib/lockdown/version.rb

@@ -2,7 +2,7 @@ module Lockdown #:nodoc:
   module VERSION #:nodoc:
     MAJOR = 0
     MINOR = 4
-    TINY  = 4
+    TINY  = 5
 
     STRING = [MAJOR, MINOR, TINY].join('.')
   end

data/website/index.txt

@@ -43,8 +43,6 @@ This will install resources such as:
 
 Please refer to the <a href="generator.html">generator page</a> for more detail.
 
-I recommend reading this page to get a feel for Lockdown's functionality.  
-
 h2. How it works
 
 Lockdown stores an array of access rights in the session.  For example, if you have a standard REST users controller, the access rights would be:
@@ -58,7 +56,7 @@ Lockdown stores an array of access rights in the session.  For example, if you h
   users/destroy (delete for Merb)
 </pre>
 
-The above list will be stored in the session as an array and each request is tested against this list.  So this means, you <strong>should not use client side session storage</strong>.  If you can, I recommend using memcache, but a database session store will suffice.
+The above list will be stored in the session as an array and each request is tested against this list.  
 
 To define access rights you need to modify lib/lockdown/init.rb.  This is the default init.rb included with Lockdown:
 <pre syntax="ruby">

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: lockdown
 version: !ruby/object:Gem::Version 
-  version: 0.4.4
+  version: 0.4.5
 platform: ruby
 authors: 
 - Andrew Stone