Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate? #114

Closed
hueniverse opened this issue Nov 4, 2017 · 4 comments
Closed

Deprecate? #114

hueniverse opened this issue Nov 4, 2017 · 4 comments
Labels
support Questions, discussions, and general support

Comments

@hueniverse
Copy link
Contributor

This module seems to be causing more confusion than utility. If we are going to keep it, someone needs to write a nice explanation on when and how to use it (vs. cookie auth, etc). Also, if we are going to keep it, please open a hapi v17 migration issue.

@hueniverse hueniverse added support Questions, discussions, and general support help wanted labels Nov 4, 2017
@MikeBazhenov
Copy link
Contributor

@hueniverse I wrote migration v17 for yar

#115

@mark-bradshaw
Copy link
Contributor

Yar remains a popular session management tool. Some people find it easier than hapi-auth-cookie, since it has more focus on a single task. It keeps a session. For people who want sessions without authentication, or want to store arbitrarily large amounts of data without wiring up a separate data store, yar is a much simpler path forward.

The main readme does have a small section at the bottom mentioning hapi-auth-cookie as an alternative. If you think it would be a help I don't mind expanding that and moving it up to the top. I definitely don't think it's good for yar to retire until hapi-auth-cookie gets split into two projects, one that manages a cookie based session and one that handles authentication. When that happens yar will be superfluous.

@mark-bradshaw
Copy link
Contributor

Closed with #115

@lock
Copy link

lock bot commented Jan 9, 2020

This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
support Questions, discussions, and general support
Projects
None yet
Development

No branches or pull requests

3 participants