In Ruby on Rails, what kind of design pattern is to use false to denote don't do DB look up and nil to denote ok to look up? -

-

in restful authentication, found current_user quite intricate that, when @current_user set false, means don't try find user again (usually db), while nil means that's ok, can again in db:

line 8 of lib/authenticated_system.rb

def current_user   @current_user ||= (login_from_session                        || login_from_basic_auth                        || login_from_cookie) unless @current_user == false end

the intricate thing is, if tries db login_from_session, etc, , can't find it, final value gets assigned @current_user nil, , method returns nil (which last evaluated value in method). unless there 2 other places in code elsewhere can set @current_user false, , trigger unless, causing whole statement return nil, while @current_user remains false, , method returns nil...

i speechless code rely on these intricate facts. false has special meaning, , nil has special meaning in code, not documented, not commented, , current_user can nil, while @current_user can continue false. design pattern, people familiar , know well?

restfulauthentication considered quite old , nasty @ point in rails history, partly because of code pointing out.

i think people advise go more modern authentication solution such devise or authlogic.


Comments

Post a Comment

Popular posts from this blog

c# - Is it possible to remove an existing registration from Autofac container builder? -

-
something along lines: builder.registertype<mytype>().as<itype>(); builder.registertype<mytype2>().as<itype>(); builder.deregistertype<mytype>().as<itype>() var container = builder.build(); var types = container.resolve<ienumerable<itype>>(); assert.istrue(types.count == 1); assert.istrue(types[0].gettype == typeof(mytype2)); scenario: go through bunch of assemblies , go register types want make sure have 1 implementation of given type. need before create container. track on own nice if autofac me bit. this cannot done directly using containerbuilder , unless start on new one. mind you, having first built container should able construct new container filtering away unwanted types , reusing registrations first container. this: ... var container = builder.build(); builder = new containerbuilder(); var components = container.componentregistry.registrations .where(cr => cr.activator.limittype != typ...
Read more

php - Mysql PK and FK char(36) vs int(10) -

-
i have read mysql can handle indexes , searches better if tables keys integers rather char(36) uuid's. is worth converting int(10)? note: use 1 server , have have plans use multiple databases concurrently therefore removing 1 of big reasons using uuid. our tables innodb if makes difference. thanks in advance. usually rdbms can handle integer keys pk more efficient, other datatypes. reason how build index column, yes: long dont require string (or other typed) keys, should use integers. however: char(36) , int(10) far away being equal, because int(10) much smaller, char(36). dont know, if require many different keys, should keep in mind. update, complete last paragraph: int(10) 32-bit, char(36) 36 - ^byte^ (= 288-bit). not mean, int consumes less space, means, char(36) has 4 times more different keys.
Read more