Skip to content
Browse files

No use case handy for justifying fresh? any more

  • Loading branch information...
1 parent d85a7ae commit 6fae0a0ec0e00db344369430e4f90e54590a5cb8 @dhh dhh committed Oct 21, 2008
Showing with 1 addition and 6 deletions.
  1. +1 −1 actionpack/CHANGELOG
  2. +0 −5 actionpack/lib/action_controller/base.rb
View
2 actionpack/CHANGELOG
@@ -1,6 +1,6 @@
*Edge*
-* Added stale?/fresh? and fresh_when methods to provide a layer of abstraction above request.fresh? and friends [DHH]. Example:
+* Added stale? and fresh_when methods to provide a layer of abstraction above request.fresh? and friends [DHH]. Example:
class ArticlesController < ApplicationController
def show_with_respond_to_block
View
5 actionpack/lib/action_controller/base.rb
@@ -1096,11 +1096,6 @@ def stale?(options)
!request.fresh?(response)
end
- # The opposite of stale? provided for parity when that feels more natural.
- def fresh?(options)
- !stale?(options)
- end
-
# Sets the etag, last_modified, or both on the response and renders a
# "304 Not Modified" response if the request is already fresh.
#

0 comments on commit 6fae0a0

Please sign in to comment.
Something went wrong with that request. Please try again.