You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Libraries should generally be careful to limit chances of naming conflicts with applications using the library and other libraries used by the application. As session data keys are only session-scoped, such naming conflicts may arise. Therefore, using a library specific namespace prefix in session keys is probably a good habit. I.e. something like projectname.key (which is the way I do it in the oauth project).
The text was updated successfully, but these errors were encountered:
Libraries should generally be careful to limit chances of naming conflicts with applications using the library and other libraries used by the application. As session data keys are only session-scoped, such naming conflicts may arise. Therefore, using a library specific namespace prefix in session keys is probably a good habit. I.e. something like projectname.key (which is the way I do it in the oauth project).
The text was updated successfully, but these errors were encountered: