Project

General

Profile

Download (1.7 KB) Statistics
| Branch: | Tag: | Revision:
#
# In several cases we want to break chain of responsibility in MVC a bit and provide
# a safe way to access current user (and maybe few more data items). Storing it as
# a global variable (or class member) is not thread-safe. Including ThreadSession::
# UserModel in models and ThreadSession::Controller in the application controller
# allows this without any concurrent issues.
#
# Idea taken from sentinent_user rails plugin.
#
# http://github.com/bokmann/sentient_user
# http://github.com/astrails/let_my_controller_go
# http://rails-bestpractices.com/posts/47-fetch-current-user-in-models
#

module Foreman
module ThreadSession

# include this in the User model
module UserModel
def self.included(base)
base.class_eval do
def self.current
Thread.current[:user]
end

def self.current=(o)
unless o.nil? || o.is_a?(self)
raise(ArgumentError, "Unable to set current User, expected class '#{self}', got #{o.inspect}")
end
Rails.logger.debug "Setting current user thread-local variable to " + (o.is_a?(User) ? o.login : 'nil')
Thread.current[:user] = o
end

# Executes given block on behalf of a different user. Example:
#
# User.as :admin do
# ...
# end
#
# Use with care!
#
# @param [String] login to find from the database
# @param [block] block to execute
def self.as(login, &do_block)
old_user = current
self.current = User.find_by_login(login)
do_block.call
self.current = old_user
end
end
end
end
end
end
(7-7/7)