| |||||||||||||
Frameworks a drawback, huh?Frameworks a drawback, huh?Posted Mar 25, 2010 1:05 UTC (Thu) by martinfick (subscriber, #4455)Parent article: Should web developers say no to cookie-based authentication?
I find it strange that the work to modify frameworks is being used as a counter argument. Isn't that the whole point of using frameworks, so that a change of this type would be "free" to the users of the framework? How valuable is the framework you are using if it can't make such a transition? Surely, it is harder to change all the custom cookie implementations out there than to change the frameworks which use cookie authentication? I would think that the ability to hide this change in a few common frameworks would be a strong argument FOR this change!
(Log in to post comments)
Frameworks a drawback, huh? Posted Mar 25, 2010 2:20 UTC (Thu) by draco (subscriber, #1792) [Link]
I recently read another paper which says something quite similar, that I thought was interesting (but disturbing):
http://www.cs.ucl.ac.uk/staff/m.handley/papers/only-just-...
Frameworks a drawback, huh? Posted Mar 28, 2010 10:15 UTC (Sun) by erwbgy (subscriber, #4104) [Link] Thanks for the link. This is an excellent paper about the Internet, the stack of protocols proposed and active and potential future problems. I would recommend others read it.
|
|||||||||||||