Library broken after cookie changes

[jhaynie]

#133 broke some of our code since we depended on the ability to set a custom cookie name for the token which was exposed before. it appears now you can't (easily) set the cookie.

looking through the changes, i guess i would now need to implement the new interfaces if i wanted my set my own cookie name?

which brings up another issue, would it be possible to semver this project to prevent major changes like this from breaking? (i see that you have a 1.0 and 2.0 release but they are old. more recent release with consistent semver would be awesome!)

[evt]

+1