Refactor cookies - 2.x codebase

[GoogleCodeExporter]

I would like to suggest a change to the way this class stores user/ 
session key info in cookies.  Looking at the javadoc for setUser() it 
appears this method used to store the user/session key info in the 
HttpSession, and my guess is someone later changed it to instead store 
user/session key info in a cookie.  I would not prefer to use 
HttpSession or cookies for controlling state in my application.  Any 
thoughts on making this configurable versus the default?

Original issue reported on code.google.com by hahna...@gmail.com on 17 Aug 2008 at 5:06

[GoogleCodeExporter]

I also do not like the current "cookie" support for FacebookWebappHelper..

I'm starting a new class called FacebookWebRequest to start breaking up the 
concerns
appropriately.  Please keep looking at the 2.0 branch and make comments.

I will eventually bring in cookie/session support because it is actually very 
useful,
but it has to be done correctly or it's buggy..

Original comment by fern...@gmail.com on 28 Aug 2008 at 9:04

• Changed state: Fixed