<?xml version="1.0" encoding="UTF-8"?>
<commit>
  <added type="array"/>
  <modified type="array">
    <modified>
      <diff>@@ -12,3 +12,5 @@ merb-auth-core/coverage
 examples/example_app/tmp
 merb-auth-core/log
 merb-auth-more/log
+merb-auth-more/coverage
+</diff>
      <filename>.gitignore</filename>
    </modified>
    <modified>
      <diff>@@ -271,9 +271,10 @@ session is available in that block as &lt;code&gt;session&lt;/code&gt;
 Really that's all there is to it.  By default this plugin doesn't actually
 authenticate anything ;)  It's up to you to get your model going, and add an
 authentication strategy.  Just remember that to login, you just use
-@session.authenticate(self)@ inside a controller.  To logout use
+@session.authenticate(request)@ inside a controller.  To logout use
 @session.abandon!@ and to force a login at any time use 
 @raise Unauthenticated, &quot;You Aren't Cool Enough&quot;@
+Be aware that strategies may throw :halt for use as a before filter...  
 
 h3. Contributors 
 </diff>
      <filename>merb-auth-core/README.textile</filename>
    </modified>
  </modified>
  <removed type="array"/>
  <parents type="array">
    <parent>
      <id>e64d3e5aa01c9c6400f7d0546f00439ef32b49a9</id>
    </parent>
  </parents>
  <author>
    <name>Daniel Neighman</name>
    <email>has.sox@gmail.com</email>
  </author>
  <url>http://github.com/hassox/merb-auth/commit/7544b586a6444dfd47143f97d5920745543ea1b7</url>
  <id>7544b586a6444dfd47143f97d5920745543ea1b7</id>
  <committed-date>2008-10-02T04:02:56-07:00</committed-date>
  <authored-date>2008-10-02T04:02:56-07:00</authored-date>
  <message>Update readme</message>
  <tree>39cc107cbfab6fe914cf6db80d6d9ca01db82d2f</tree>
  <committer>
    <name>Daniel Neighman</name>
    <email>has.sox@gmail.com</email>
  </committer>
</commit>
